-
Notifications
You must be signed in to change notification settings - Fork 46
allow for custom cluster domain for agent to api connection #736
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
base: develop
Are you sure you want to change the base?
allow for custom cluster domain for agent to api connection #736
Conversation
We tested this patch in our production and it did solve our problems. We did not fork the helm chart but instead we usually render them and edit them by hand. If this is something you'd be willing to accept upstream, I can add it to the helm chart as well. |
Thanks for the PR @mikn! Supporting this setting is something we are open to. I think adding in a bit more testing and changes to the helm chart would get us to a good place for merging this change. Can you confirm with some logs/output that a basic cluster works with the default and then provide an example of the custom cluster domain working? You can redact the custom name from the logs, I'd just like to document that we knew the change works for the PR. |
Hey @mikn, I just wanted to check back in on if you got any testing done for this that you can share? |
Hi @yeazelm ! Sorry no - we have been extremely resource constrained for a while - but we have a longer weekend this weekend (and have finally caught up on work) so I should have some time to catch up to the outstanding issues wrt Bottlerocket. |
Here are the proofs:
With custom domain:
I removed the object dump of the BottlerocketShadow object for brevity and altered the custom domain for secrecy. The reason they are different outputs from the two is mostly because the BRS and the cluster I produced the custom proof on has existed for a while now. |
Hi again @yeazelm think it is possible to move this forward? 🙏 |
Looks good to me! Thanks for adding in the testing! |
Issue number: #735
Description of changes:
Introduces a
KUBERNETES_SERVICE_CLUSTER_DOMAIN
env var that allows you to set the service cluster domain for the cluster which it uses to talk to the brupop apiserver.Testing done:
None yet.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.