Fix, replacing the kubectl plugin with recommended cert-manager binary #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
July 23, 2024 17:06
…mand executed with sudo
locohamster
force-pushed
the
kube-cert-manager-ci-fix
branch
from
17399aa to
428a59f
Compare
|
raczu
added
scope: ci
raczu
added
the
status: ready for merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cert-manager has stopped releasing the kubectl plugin in favor of the standalone binary.
Project CI jobs were failing.
Recommended binary was added and used instead, unfortunately the cmctl is not a kubectl plugin so we need to configure KUBECONFIG for it and mane sure that command with sudo will access env variable.
Another approach would be coping microk8s config to default path in /root/.kube it was not chosen.