-
Notifications
You must be signed in to change notification settings - Fork 899
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
kubectl apply --dry-run=client attempts to connect to the server #1589
Comments
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
Please see the group list for a listing of the SIGs, working groups, and committees available. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-kind bug AIUI: |
Well then it's not really a client side validation is it. Is there any kind of validation I can do without giving pre approval PRs cluster credentials? |
There's a better home for this request. |
/remove-kind support Yes it is known that dry-run=client still requires to access to cluster (see more: kubernetes/kubernetes#123337 (comment)). |
/sig cli |
What happened?
I have an environment which doesn't have server credentials for security reasons for running PR checks on our gitops repository (post-merge actual application has a separate environment with credentials). I would like to do a dry-run check on the validity of the configuration in the PR, without having cluster credentials.
When I ran kubectl apply -f output --dry-run=client it prompted for connection details and failed
What did you expect to happen?
I expected --dry-run=client not to connect to the server
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
No response
Kubernetes version
I'm using 1.26.14, but I also tested with 1.30.0
Cloud provider
n/a
OS version
Linux RHEL8
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: