We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
flux build kustomization --dry-run
#3317 implemented a --dry-run flag that states:
--dry-run
If implemented user will be able to use flux build kustomization without any connection to the cluster.
This seems to be incorrect:
$ flux build kustomization base --path clusters/stg --kustomization-file clusters/stg/base.yaml --dry-run ✗ kubernetes client initialization failed: Get "https://kubernetes.docker.internal:6443/api?timeout=32s": dial tcp 127.0.0.1:6443: connect: connection refused
flux build kustomization
Should render some yamls.
No response
macOS and Ubuntuf
0.37.0
► checking prerequisites ✗ Kubernetes API call failed: Get "https://kubernetes.docker.internal:6443/version": dial tcp 127.0.0.1:6443: connect: connection refused ► checking controllers ► checking crds ✗ check failed
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
#3317 implemented a
--dry-run
flag that states:This seems to be incorrect:
Steps to reproduce
flux build kustomization
with a dead kubeconfig and watch it fail.Expected behavior
Should render some yamls.
Screenshots and recordings
No response
OS / Distro
macOS and Ubuntuf
Flux version
0.37.0
Flux check
► checking prerequisites
✗ Kubernetes API call failed: Get "https://kubernetes.docker.internal:6443/version": dial tcp 127.0.0.1:6443: connect: connection refused
► checking controllers
► checking crds
✗ check failed
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: