INSTALL.md: Clarify requirements for namespaced installs #88
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.
Hi!
We twice (on different K8s clusters) ran into the same issue with a Helm-based, namespaced Operator install where the CPA CRD would never create the autoscaler Pod, and nothing useful would be logged. After some trial and error, we discovered that we also needed to install the Operator into the
default
namespace, together with the namespaced install. Once both installs were in place, the autoscaler Pod magically appeared and started doing its nice work.Making this small PR so others don't run into the same issue. Or, if you have any suggestions, please advise!
Thank you for the amazing project! It's the least we can give back! :)