-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Ability to disable https://kubernetes.default.svc #7571
Comments
Wow thats an interesting request. Happy to help. |
Changes probably needed here: Lines 55 to 79 in fe3cc72
|
Hi there, to reiterate -- if the user provides Could you talk a bit more about this flag/option to disable |
@pixelsoccupied This will be a new key, e.g. "inClusterServerAddressAllowed", in ArgoCD ConfigMap so you can update it on the fly as well. |
I created a draft PR in #7620. Feel free to leave your feedback there. |
Signed-off-by: Yuan Tang <[email protected]>
Signed-off-by: Yuan Tang <[email protected]>
… (argoproj#7620) Signed-off-by: Yuan Tang <[email protected]>
… (argoproj#7620) Signed-off-by: Yuan Tang <[email protected]> Signed-off-by: wojtekidd <[email protected]>
This does not seem to prevent Application from being created using this cluster. The only thing it is doing iis hiding the cluster from the list of available clusters. #21207 As it is documented, it would seem that this feature should prevent new applications from being created and should not sync existing applications with the in-cluster destination. |
Summary
Many users run Argo CD in a mode where that Argo CD instance doesn't ever need or want to deploy Applications to the same cluster Argo CD is running in (e.g. Intuit does this). For these users, the
https://kubernetes.default.svc
should be disabled and removed as an option.Motivation
The ability to disable https://kubernetes.default.svc is both a security improvement as well as usability improvement since end-users do not see cluster which they cannot use.
Proposal
Argo CD should have an option to disable https://kubernetes.default.svc as a managed cluster so that it becomes impossible to deploy to.
The text was updated successfully, but these errors were encountered: