cannot run second ingress controller via nginx-helm-operator

[NICK0TIN]

Version

app.kubernetes.io/version: 4.0.1
helm.sdk.operatorframework.io/chart: nginx-ingress
helm.sh/chart: nginx-ingress-2.0.1

What Kubernetes platforms are you running on?

Openshift

Steps to reproduce

Via the OpenShift operatorhub I try to create 2 or more NginxIngress object that will trigger the helm chart to deploy the Nginx controller.

The 2nd controller I try to deploy fails, because the first SA "nginx-ingress" is created and managed by the first Helm chart.

I read that this can be configured by setting the values file:

controller:
  serviceAccount:
    ## Autogenerated if not set or set to "".
    name: nginx-ingress

However no matter the name given, the SA will always be created as nginx-ingress.

Steps to reproduce:

Create any NginxIngress on OpenShift and give a different name than nginx-ingress.

controller:
  serviceAccount:
    ## Autogenerated if not set or set to "".
    name: nginx-ingress-test

[NICK0TIN]

Further investigation learns me that the name of the serviceAccount is overwritten:

Warning OverrideValuesInUse 9m22s (x5 over 9m26s) nginxingress-controller Chart value "controller.serviceAccount.name" overridden to "nginx-ingress" by operator's watches.yaml

Is this intended behaviour? Does this mean I cannot create a second ingress controller via the operator?

[pdabelf5]

Hi @NICK0TIN Thank you for creating an issue. Could you please confirm if you are following the documentation for running multiple ingress controllers in the same namespace?