Job not being scheduled to elastic agent about kubernetes-elastic-agents HOT 7 CLOSED

I could be wrong, but the chosen image (travix/gocd-agent-gcloud-jdk-8) doesn't seem to be setup for elastic agents. So, it's probably coming up, but doesn't know how to autoregister using the environment variables that the plugin is providing while starting it.

This section in the docker elastic agent's README mentions what is needed to use a custom docker image with elastic agents. This is how those variables are used in GoCD's official docker image.

Maybe we need to mention the same in the README of these elastic agents. /cc @sheroy

from kubernetes-elastic-agents.

@cfontes, this is correct. We'll add these instructions in the k8s Elastic Agent README. For now, can you confirm that using the official GoCD agent Docker image works for you?

from kubernetes-elastic-agents.

@arvindsv Thanks for the details

@sheroy just tried with gocd/gocd-agent-docker-dind:v18.6.0 and it works.

I've seen that guide while troubleshooting it yesterday, but I it was not clear to me with my limited knoweldge what I was missing or why. I will try to adapt it and try again.

from kubernetes-elastic-agents.

@sheroy If it's possible to provide a template for converting a non-elastic-agent Docker image to an elastic agent one, then we should. I mean, if it's just the creation of an autoregister.properties file in the right place, we might be able to do that. Let me know if you're ok taking a look at it.

@cfontes The agent is the same. It's just that in the context of it being started from an elastic agent plugin, the environment variables it needs to use to connect to the GoCD server are different. The Docker images which are used in the elastic agent context make sure that the environment variables are used.

from kubernetes-elastic-agents.

@arvindsv

I just got it working. I love this feature, thank you for it!

Would be great to have a way to do it in the Helm Chart, I've added a config map in my case with the script to generate the config file, but the agent container needs to run the script so that requires some specific changes to it.

Some kind of side car, or init container that you could just copy paste maybe.

from kubernetes-elastic-agents.

@arvindsv Yes, I can look into this soon.

@cfontes, can I also catch up with you at some point to talk to you about your use case and how you are using our K8S plugin?

from kubernetes-elastic-agents.

@sheroy, as soon as I have something more solid we sure can.

Thanks I will close this issue ;)

from kubernetes-elastic-agents.