[stable/nginx-ingress] Fix ClusterRole creation when using namespaces (#19886)

* [stable/nginx-ingress] Fix ClusterRole creation when using namespaces

We want to be able to choose to deploy to a namespace and still opt-in
to ClusterRole creation.

Fixes: https://github.com/helm/charts/issues/18420

Signed-off-by: Graham McGregor <graham@gmcgregor.ca>

Co-authored-by: Madeline Van Der Paelt <madd_y@hotmail.com>

* [stable/nginx-ingress] Bump nginx-ingress chart version

Signed-off-by: Graham McGregor <graham@gmcgregor.ca>

Co-authored-by: Madeline Van Der Paelt <madd_y@hotmail.com>

Co-authored-by: maddster82 <madd_y@hotmail.com>

stable/nginx-ingress/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v1
 name: nginx-ingress
-version: 1.27.2
+version: 1.28.0
 appVersion: 0.26.2
 home: https://github.com/kubernetes/ingress-nginx
 description: An nginx Ingress controller that uses ConfigMap to store the nginx configuration.

stable/nginx-ingress/templates/clusterrole.yaml

@@ -1,4 +1,4 @@
-{{- if and .Values.rbac.create (not .Values.controller.scope.enabled) -}}
+{{- if .Values.rbac.create -}}
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
 metadata:

stable/nginx-ingress/templates/clusterrolebinding.yaml

@@ -1,4 +1,4 @@
-{{- if and .Values.rbac.create (not .Values.controller.scope.enabled) -}}
+{{- if .Values.rbac.create -}}
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata: