Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for multiple clusters #43

Closed
joaoubaldo opened this issue Apr 4, 2018 · 11 comments
Closed

Support for multiple clusters #43

joaoubaldo opened this issue Apr 4, 2018 · 11 comments

Comments

@joaoubaldo
Copy link

I have a scenario where I need different gocd agents for different environments due to networking policies (as in, qa agents only see qa resources, same for staging and production). Is support for multiple clusters planned? Is there any way to support this scenario with the current plugin version?

@varshavaradarajan
Copy link
Contributor

@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?

@arvindsv
Copy link
Member

arvindsv commented Apr 4, 2018

@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

@varshavaradarajan
Copy link
Contributor

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

@joaoubaldo
Copy link
Author

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

@cfontes
Copy link

cfontes commented Oct 19, 2018

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.

@arvindsv
Copy link
Member

@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.

@saifally
Copy link

saifally commented Oct 20, 2018

@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.

@cfontes
Copy link

cfontes commented Oct 20, 2018

@arvindsv and @saifally

Great, thanks, I will be following this PR.

@wstewartii
Copy link

Any update on this?

@bdpiprava
Copy link
Contributor

@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.

@varshavaradarajan
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants