kubeapps: bump chart version to 3.5.1

bitnami/kubeapps/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v1
 name: kubeapps
-version: 3.5.0
-appVersion: v1.9.0
+version: 3.5.1
+appVersion: v1.9.1
 description: Kubeapps is a dashboard for your Kubernetes cluster that makes it easy to deploy and manage applications in your cluster using Helm
 icon: https://raw.githubusercontent.com/kubeapps/kubeapps/master/docs/img/logo.png
 keywords:

bitnami/kubeapps/README.md

@@ -46,9 +46,9 @@ To install the chart with the release name `kubeapps`:
 
 For Helm 2:
 
-```console
-$ helm repo add bitnami https://charts.bitnami.com/bitnami
-$ helm install --name kubeapps --namespace kubeapps bitnami/kubeapps
+```bash
+helm repo add bitnami https://charts.bitnami.com/bitnami
+helm install --name kubeapps --namespace kubeapps bitnami/kubeapps
 ```
 
 > **IMPORTANT** This assumes an insecure Helm 2 installation, which is not recommended in production. See [the documentation to learn how to secure Helm 2 and Kubeapps in production](https://github.com/kubeapps/kubeapps/blob/master/docs/user/securing-kubeapps.md).
@@ -73,8 +73,8 @@ For a full list of configuration parameters of the Kubeapps chart, see the [valu
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
-```console
-$ helm install kubeapps --namespace kubeapps \
+```bash
+helm install kubeapps --namespace kubeapps \
   --set assetsvc.service.port=9090 \
     bitnami/kubeapps
 ```
@@ -83,8 +83,8 @@ The above command sets the port for the assetsvc Service to 9090.
 
 Alternatively, a YAML file that specifies the values for parameters can be provided while installing the chart. For example,
 
-```console
-$ helm install kubeapps --namespace kubeapps -f custom-values.yaml bitnami/kubeapps
+```bash
+helm install kubeapps --namespace kubeapps -f custom-values.yaml bitnami/kubeapps
 ```
 
 ## Configuration and installation details
@@ -125,8 +125,8 @@ The simplest way to expose the Kubeapps Dashboard is to assign a LoadBalancer ty
 
 Wait for your cluster to assign a LoadBalancer IP or Hostname to the `kubeapps` Service and access it on that address:
 
-```console
-$ kubectl get services --namespace kubeapps --watch
+```bash
+kubectl get services --namespace kubeapps --watch
 ```
 
 #### Ingress
@@ -157,15 +157,15 @@ You can upgrade Kubeapps from the Kubeapps web interface. Select the namespace i
 
 You can also use the Helm CLI to upgrade Kubeapps, first ensure you have updated your local chart repository cache:
 
-```console
-$ helm repo update
+```bash
+helm repo update
 ```
 
 Now upgrade Kubeapps:
 
-```console
-$ export RELEASE_NAME=kubeapps
-$ helm upgrade $RELEASE_NAME bitnami/kubeapps
+```bash
+export RELEASE_NAME=kubeapps
+helm upgrade $RELEASE_NAME bitnami/kubeapps
 ```
 
 If you find issues upgrading Kubeapps, check the [troubleshooting](#error-while-upgrading-the-chart) section.
@@ -174,13 +174,15 @@ If you find issues upgrading Kubeapps, check the [troubleshooting](#error-while-
 
 To uninstall/delete the `kubeapps` deployment:
 
-```console
+```bash
 # For Helm 2
-$ helm delete --purge kubeapps
+helm delete --purge kubeapps
+
 # For Helm 3
-$ helm uninstall kubeapps
+helm uninstall kubeapps
+
 # Optional: Only if there are no more instances of Kubeapps
-$ kubectl delete crd apprepositories.kubeapps.com
+kubectl delete crd apprepositories.kubeapps.com
 ```
 
 The first command removes most of the Kubernetes components associated with the chart and deletes the release. After that, if there are no more instances of Kubeapps in the cluster you can manually delete the `apprepositories.kubeapps.com` CRD used by Kubeapps that is shared for the entire cluster.
@@ -189,8 +191,8 @@ The first command removes most of the Kubernetes components associated with the
 
 If you have dedicated a namespace only for Kubeapps you can completely clean remaining completed/failed jobs or any stale resources by deleting the namespace
 
-```console
-$ kubectl delete namespace kubeapps
+```bash
+kubectl delete namespace kubeapps
 ```
 
 ## Troubleshooting
@@ -211,7 +213,7 @@ Error: namespaces "kubeapps" is forbidden: User "system:serviceaccount:kube-syst
 
 This usually is an indication that Tiller was not installed with enough permissions to create the resources required by Kubeapps. In order to install Kubeapps, tiller will need to be able to install Custom Resource Definitions cluster-wide, as well as manage app repositories in your kubeapps namespace. The easiest way to enable this in a development environment is install Tiller with elevated permissions (e.g. as a cluster-admin). For example:
 
-```
+```bash
 kubectl -n kube-system create sa tiller
 kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller
 helm init --service-account tiller
@@ -221,14 +223,14 @@ but for a production environment you can assign the specific permissions so that
 
 It is also possible, though less common, that your cluster does not have Role Based Access Control (RBAC) enabled. To check if your cluster has RBAC you can execute:
 
-```console
-$ kubectl api-versions
+```bash
+kubectl api-versions
 ```
 
 If the above command does not include entries for `rbac.authorization.k8s.io` you should perform the chart installation by setting `rbac.create=false`:
 
-```console
-$ helm install --name kubeapps --namespace kubeapps bitnami/kubeapps --set rbac.create=false
+```bash
+helm install --name kubeapps --namespace kubeapps bitnami/kubeapps --set rbac.create=false
 ```
 
 ### Error while upgrading the Chart
@@ -239,13 +241,13 @@ It is possible that when upgrading Kubeapps an error appears. That can be caused
 
 1.  (Optional) Backup your personal repositories (if you have any):
 
-```console
+```bash
 kubectl get apprepository --namespace kubeapps -o yaml <repo name> > <repo name>.yaml
 ```
 
 2.  Delete Kubeapps:
 
-```console
+```bash
 helm del --purge kubeapps
 ```
 
@@ -253,7 +255,7 @@ helm del --purge kubeapps
 
 > **Warning**: Don't execute this step if you have more than one Kubeapps installation in your cluster.
 
-```console
+```bash
 kubectl delete crd apprepositories.kubeapps.com
 ```
 
@@ -261,20 +263,20 @@ kubectl delete crd apprepositories.kubeapps.com
 
 > **Warning**: Don't execute this step if you have workloads other than Kubeapps in the `kubeapps` namespace.
 
-```console
+```bash
 kubectl delete namespace kubeapps
 ```
 
 5.  Install the latest version of Kubeapps (using any custom modifications you need):
 
-```console
+```bash
 helm repo update
 helm install --name kubeapps --namespace kubeapps bitnami/kubeapps
 ```
 
 6.  (Optional) Restore any repositories you backed up in the first step:
 
-```console
+```bash
 kubectl apply -f <repo name>.yaml
 ```
 

bitnami/kubeapps/values.yaml

@@ -185,7 +185,7 @@ apprepository:
   image:
     registry: docker.io
     repository: bitnami/kubeapps-apprepository-controller
-    tag: 1.9.0-scratch-r0
+    tag: 1.9.1-scratch-r0
   ## Kubeapps assets synchronization tool
   ## Image used to perform chart repository syncs
   ## ref: https://hub.docker.com/r/bitnami/kubeapps-asset-syncer/tags/
@@ -193,7 +193,7 @@ apprepository:
   syncImage:
     registry: docker.io
     repository: bitnami/kubeapps-asset-syncer
-    tag: 1.9.0-scratch-r0
+    tag: 1.9.1-scratch-r0
   ## Initial charts repo proxies to configure
   ##
   initialReposProxy:
@@ -281,7 +281,7 @@ kubeops:
   image:
     registry: docker.io
     repository: bitnami/kubeapps-kubeops
-    tag: 1.9.0-scratch-r0
+    tag: 1.9.1-scratch-r0
   service:
     port: 8080
   resources:
@@ -323,7 +323,7 @@ tillerProxy:
   image:
     registry: docker.io
     repository: bitnami/kubeapps-tiller-proxy
-    tag: 1.9.0-scratch-r0
+    tag: 1.9.1-scratch-r0
 
   ## Tiller Proxy service parameters
   ##
@@ -397,7 +397,7 @@ assetsvc:
   image:
     registry: docker.io
     repository: bitnami/kubeapps-assetsvc
-    tag: 1.9.0-scratch-r0
+    tag: 1.9.1-scratch-r0
   ## Assetsvc service parameters
   ##
   service:
@@ -457,7 +457,7 @@ dashboard:
   image:
     registry: docker.io
     repository: bitnami/kubeapps-dashboard
-    tag: 1.9.0-debian-10-r0
+    tag: 1.9.1-debian-10-r0
   ## Dashboard service parameters
   ##
   service: