Support for multiple clusters about kubernetes-elastic-agents HOT 11 CLOSED

@varshavaradarajan Yes, sure. The cluster information can be optional in the EA profiles, though. So that those who don't need them don't need to set it.

/cc @sheroy

from kubernetes-elastic-agents.

@wstewartii - We are working to support multi-cluster for the elastic agent plugin in the upcoming release. See issue gocd/gocd#5538 for more information. The plugin will be updated as well, to support the same.

from kubernetes-elastic-agents.

With the release of GoCD 19.3.0 and the latest k8s plugin, multi cluster support has been added. This issue can now be closed.

cc @GaneshSPatil

from kubernetes-elastic-agents.

@joaoubaldo - with the current plugin version, there isn't. I was thinking whether we could have the cluster information in the elastic agent profile in GoCD so that we can have different profiles pointing to different clusters. This is useful if people have clusters set up on multiple platforms. I think a use case for it could be to test a k8s deployment on different platforms. @akshaydewan, @arvindsv , @bdpiparva , @GaneshSPatil - WDYT?

from kubernetes-elastic-agents.

Yeah - similar to how we did it with ecs elastic agent. Some properties can be overridden at the elastic agent profile level.

from kubernetes-elastic-agents.

That sounds good. I will keep an eye on this, thanks.

from kubernetes-elastic-agents.

I am also very interested on this feature.

I am running GoCD on one cluster that deploys to several other clusters. Right now testing is a bit hard as my test containers from the devops cluster need to have a direct network connection to all clusters, which is not the most secure approach.

The ideal would be to have the test container running in the cluster it will be testing itself.

from kubernetes-elastic-agents.

@cfontes I see that the elastic agent profile is being updated with some more settings in this pull request #60.

@GaneshSPatil @sheroy Is that the right place to add support for a different cluster? Or, does it need more information such as credentials, etc.

from kubernetes-elastic-agents.

@arvindsv . In my opinion that is the right place. I will be adding that as part of #60 . I have the credentials and all details at the elastic profile level. I have to add the front end code to capture Cluster Url and CA. However , first thing first, I have to fix some of the review comments from @GaneshSPatil first.

from kubernetes-elastic-agents.

@arvindsv and @saifally

Great, thanks, I will be following this PR.

from kubernetes-elastic-agents.

Any update on this?

from kubernetes-elastic-agents.