Use upstream rbac.create value

In any case, Gitlab::Kubernetes::Helm::InstallCommand requires rbac or
not to be specified which will set the approriate rbac.create value on
installation or upgrade of apps

spec/models/clusters/applications/jupyter_spec.rb

@@ -91,7 +91,6 @@ describe Clusters::Applications::Jupyter do
       it 'includes valid values' do
         expect(values).to include('ingress')
         expect(values).to include('hub')
-        expect(values).to include('rbac')
         expect(values).to include('proxy')
         expect(values).to include('auth')
         expect(values).to include('singleuser')
@@ -111,7 +110,6 @@ describe Clusters::Applications::Jupyter do
       it 'includes valid values' do
         expect(values).to include('ingress')
         expect(values).to include('hub')
-        expect(values).to include('rbac')
         expect(values).to include('proxy')
         expect(values).to include('auth')
         expect(values).to include('singleuser')

vendor/ingress/values.yaml

@@ -7,6 +7,3 @@ controller:
   podAnnotations:
     prometheus.io/scrape: "true"
     prometheus.io/port: "10254"
-
-rbac:
-  create: false

vendor/jupyter/values.yaml

-rbac:
-  enabled: false
-
 hub:
   extraEnv:
     JUPYTER_ENABLE_LAB: 1

vendor/prometheus/values.yaml

@@ -12,9 +12,6 @@ nodeExporter:
 pushgateway:
   enabled: false
 
-rbac:
-  create: false
-
 server:
   fullnameOverride: "prometheus-prometheus-server"
   image:

vendor/runner/values.yaml

@@ -11,7 +11,6 @@ checkInterval: 3
 
 ## For RBAC support
 rbac:
-  create: false
   clusterWideAccess: false
 
 ## Configuration for the Pods that that the runner launches for each new job