The CACertManager ensures the CA Cert is created and managed and by default it assumes this is done in the emissary-system namespace.
We missed passing the configured namespace into the CACertManager so it would fail when users installed the emissary-apiext into a different namespace than emissary-system.
Related Issues
N/A
Testing
CI is green
Checklist
[ ] Does my change need to be backported to a previous release?
[ ] I made sure to update CHANGELOG.md.
[x] This is unlikely to impact how Ambassador performs at scale.
[ ] My change is adequately tested.
[ ] I updated DEVELOPING.md with any any special dev tricks I had to use to work on this code efficiently.
[x] The changes in this PR have been reviewed for security concerns and adherence to security best practices.
Description
The CACertManager ensures the CA Cert is created and managed and by default it assumes this is done in the emissary-system namespace.
We missed passing the configured namespace into the CACertManager so it would fail when users installed the emissary-apiext into a different namespace than emissary-system.
Related Issues
N/A
Testing
CI is green
Checklist
CHANGELOG.md.DEVELOPING.mdwith any any special dev tricks I had to use to work on this code efficiently.