Symptoms
When deploying or upgrading an Event Streams instance to version 11.7.0, you might see an error message similar to the following example:
The Node Pool Name kafka already exists in the namespace cp4i
This error prevents the creation or reconciliation of the EventStreams custom resource.
Causes
Event Streams uses the app.kubernetes.io/instance label to validate node pool uniqueness. During reconciliation, the operator checks if a node pool with the same name already exists in your namespace and compares the label value against the Event Streams instance name.
In some environments, especially those managed by using tools such as Argo CD, this label might be overwritten or manually modified. If the label value does not match the Event Streams instance name, the validation fails and incorrectly reports that the node pool already exists.
Resolving the problem
To resolve this issue, either upgrade to Event Streams version 11.8.0 or ensure that the value of the app.kubernetes.io/instance label on the node pool matches the name of the Event Streams instance.
For example, if your instance name is kafka-es, the label must be:
app.kubernetes.io/instance: kafka-es