Hello, how do I add my glossary of terms to an eks? Should I connect to the node or directly to a POD?

There should be a GMS service. You can connect to that and run an ingestion similar to ingestions for any database. Here are docs https://datahubproject.io/docs/metadata-ingestion/source_docs/business_glossary/

where should I put my YAML file?? or you could replace the file with the entire content of the YAML

There are 2 yaml files here - recipe file, glossary files. Where are you keeping them currently?

I was talking about the yaml of the file that contains all the formatting of the glossary of terms

Usually it is recommended to store these glossary of terms file in version control somewhere (like git). When you running ingestion of business glossary recipes you checkout the git repository and use it to run your ingestion

Sure, but how do I use it? because I have everything displayed in an EKS, I don't know where to leave my glossary file so that the front recognizes it or can I pass an s3 in the path?

how do I use it

What is "it"? The file containing the glossary terms?

I don't know where to leave my glossary file so that the front recognizes

Have you seen this https://datahubproject.io/docs/metadata-ingestion/source_docs/business_glossary/? You don't leave the file anywhere. You ingest it into DataHub similar to other sources

and could the glossary be ingested from the API through port 8080?

Yes the source uses port 8080 if you use the rest sink

hello again, I am trying to ingest the glossary of terms through the API and it is giving me this error "message": "com.linkedin.metadata.entity.ValidationException: Failed to validate record with class com.linkedin.entity.Entity: ERROR :: /value/com.linkedin.metadata.snapshot.GlossaryTermSnapshot/glossaryTermInfo :: unrecognized field found but not allowed\nERROR :: /value/com.linkedin.metadata.snapshot.GlossaryTermSnapshot/urn :: field is required but not found and has no default value\nERROR :: /value/com.linkedin.metadata.snapshot. GlossaryTermSnapshot/aspects :: field is required but not found and has no default value\n", "status": 422