home/charts
2
0
Fork 0
mirror of https://github.com/wahyd4/charts.git synced 2026-08-22 19:48:25 +10:00
Code Issues Packages Projects Releases Wiki Activity

kubeapps: bump chart version to 4.0.1

Browse Source
This commit is contained in:
kubernetes-bitnami
2020-09-29 10:01:20 +00:00
parent ed8cbbaaa5
commit f45925c70b
3 changed files with 8 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/kubeapps/Chart.yaml
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: kubeapps
version: 4.0.0
appVersion: v2.0.0-beta.1
version: 4.0.1
appVersion: v2.0.0-beta.2
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
+1 -11
View File
@@ -179,17 +179,7 @@ Or:
Error: namespaces "kubeapps" is forbidden: User "system:serviceaccount:kube-system:default" cannot get namespaces in the namespace "kubeapps"
```
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
```
but for a production environment you can assign the specific permissions so that tiller can [manage CRDs on the cluster](https://github.com/kubeapps/kubeapps/blob/master/docs/user/manifests/openshift-tiller-with-crd-rbac.yaml) as well as [create app repositories in your Kubeapps namespace](https://github.com/kubeapps/kubeapps/blob/master/docs/user/manifests/openshift-tiller-with-apprepository-rbac.yaml) (examples are from our in development support for OpenShift).
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:
It is possible, though uncommon, that your cluster does not have Role Based Access Control (RBAC) enabled. To check if your cluster has RBAC you can execute:
```bash
kubectl api-versions
bitnami/kubeapps/values.yaml
+5 -5
View File
@@ -219,7 +219,7 @@ apprepository:
image:
registry: docker.io
repository: bitnami/kubeapps-apprepository-controller
tag: 2.0.0-scratch-r0
tag: 2.0.0-scratch-r1
## Specify a imagePullPolicy
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
@@ -231,7 +231,7 @@ apprepository:
syncImage:
registry: docker.io
repository: bitnami/kubeapps-asset-syncer
tag: 2.0.0-scratch-r0
tag: 2.0.0-scratch-r1
## Specify a imagePullPolicy
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
@@ -324,7 +324,7 @@ kubeops:
image:
registry: docker.io
repository: bitnami/kubeapps-kubeops
tag: 2.0.0-scratch-r0
tag: 2.0.0-scratch-r1
## Specify a imagePullPolicy
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
@@ -368,7 +368,7 @@ assetsvc:
image:
registry: docker.io
repository: bitnami/kubeapps-assetsvc
tag: 2.0.0-scratch-r0
tag: 2.0.0-scratch-r1
## Specify a imagePullPolicy
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
@@ -433,7 +433,7 @@ dashboard:
image:
registry: docker.io
repository: bitnami/kubeapps-dashboard
tag: 2.0.0-debian-10-r0
tag: 2.0.0-debian-10-r4
## Specify a imagePullPolicy
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##