feat: support running in non-default namespace #20
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
|
@mikouaj, we would prefer if a structured file format for configuring the controller is avoided, as it is impossible to patch with kustomize. The controller config is also deprecated (or about to be) in upstream controller-runtime, ref. kubernetes-sigs/controller-runtime#895. I down-voted #2 just now for this reason. |
This was referenced Feb 9, 2024
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.
I initially tried to run the operator in another namespace than
kube-startup-cpu-boost-system, but this failed because the namespace is hardcoded when supplied to the cert-rotator.This PR suggests to use the downwardAPI to inject the current namespace as an environment variable to the workload. I have kept the hardcoded namespace name as a default for now.