Closed matthewpwilson closed 4 years ago
@cvignola who can take a look at this? It's blocking our usage of kAppNav in a Strimzi-based scenario.
@ianpartridge @paulben is investigating.
Great, thanks!
I've recreated it. Working on a fix.
How's it going? Do you have a test version of kAppNav we could try out?
Hi @rlcundiff could you point us at a fixed version of kAppNav that we could download and test out please?
If I install kAppNav into my OCP 4.2 cluster and create an application CR, kAppNav adds annotations to StatefulSets that are not part of the application (i.e. they do not match the selector) but in the same namespace. In this case the StatefulSet is managed by another operator, and the presence of the unexpected annotations causes the operator to recreate the resource each time they are added!
Should kAppNav be adding these annotations to resources it doesn't own at all?
Application CR:
StatefulSet metadata: