We have used Linkerd Stable 2.14 but installed our CRD’s and controlplane in a custom namespace named l12m-linkerd.
We now want to upgrade to version 2.15 of BEL and we get now the error “Namespace must be ‘linkerd’”
I see this error is being generated by the NOTES.txt file in the helmchart. What is the reason that this is obligatory in BEL and not in the opensource version of Linkerd? It’s for us important to be able to customize the namespace to differentiate client namespaces and our own.
Is there something I’m missing? Is there a way I can ignore this NOTES.txt file in flux?
I believe this is to simplify a lot of the configuration that the lifecycle operator needs to perform its duties. If you want to skip the lifecycle automation aspect, I would try just removing that section and seeing if everything else works normally, though you’ll be going off the golden path in that case.
As William mentioned previously, this was put into place to help provide guard rails for first-time implementations, and to help the lifecycle operator perform its duties and validate configs.
That being said, we’ve heard the feedback from our users and plan to relax this requirement in an upcoming release, though note this will take you off the recommended golden path and can potentially make troubleshooting slightly more difficult down the road.