From e68355bf81df8b77b870700059382abb39615289 Mon Sep 17 00:00:00 2001 From: kubeapps-bot Date: Wed, 1 Mar 2023 19:50:11 +0000 Subject: [PATCH 1/2] bump chart version to 12.2.6 Signed-off-by: kubeapps-bot --- chart/kubeapps/Chart.lock | 10 +-- chart/kubeapps/Chart.yaml | 2 +- chart/kubeapps/README.md | 145 +++++++++++++++++-------------------- chart/kubeapps/values.yaml | 4 +- 4 files changed, 74 insertions(+), 87 deletions(-) diff --git a/chart/kubeapps/Chart.lock b/chart/kubeapps/Chart.lock index 3a20596e922..688e55104e1 100644 --- a/chart/kubeapps/Chart.lock +++ b/chart/kubeapps/Chart.lock @@ -1,12 +1,12 @@ dependencies: - name: redis repository: https://charts.bitnami.com/bitnami - version: 17.7.1 + version: 17.8.0 - name: postgresql repository: https://charts.bitnami.com/bitnami - version: 12.1.14 + version: 12.2.1 - name: common repository: https://charts.bitnami.com/bitnami - version: 2.2.2 -digest: sha256:3e095f50cf5e95a3d1e018dea960945a987f9663d64f28e9cb8cf482acd4625b -generated: "2023-02-04T16:24:28.966071279Z" + version: 2.2.3 +digest: sha256:0e73ac82a99c3fdcbf665e07cbbc0aadb98c55bd69560bab5002e2199f800edd +generated: "2023-02-27T00:20:41.698703902Z" diff --git a/chart/kubeapps/Chart.yaml b/chart/kubeapps/Chart.yaml index 222dcd61d12..3633b4b3781 100644 --- a/chart/kubeapps/Chart.yaml +++ b/chart/kubeapps/Chart.yaml @@ -32,4 +32,4 @@ maintainers: name: kubeapps sources: - https://github.com/vmware-tanzu/kubeapps -version: 12.2.5-dev0 +version: 12.2.6 diff --git a/chart/kubeapps/README.md b/chart/kubeapps/README.md index e87304e100c..cef8e30ad56 100644 --- a/chart/kubeapps/README.md +++ b/chart/kubeapps/README.md @@ -1,3 +1,5 @@ + + # Kubeapps packaged by Bitnami Kubeapps is a web-based UI for launching and managing applications on Kubernetes. It allows users to deploy trusted applications and operators to control users access to the cluster. @@ -5,12 +7,12 @@ Kubeapps is a web-based UI for launching and managing applications on Kubernetes [Overview of Kubeapps](https://github.com/vmware-tanzu/kubeapps) - + ## TL;DR ```console -$ helm repo add my-repo https://charts.bitnami.com/bitnami -$ helm install my-release my-repo/kubeapps --namespace kubeapps --create-namespace +helm repo add my-repo https://charts.bitnami.com/bitnami +helm install my-release my-repo/kubeapps --namespace kubeapps --create-namespace ``` > Check out the [getting started](https://github.com/vmware-tanzu/kubeapps/blob/main/site/content/docs/latest/tutorials/getting-started.md) to start deploying apps with Kubeapps. @@ -44,8 +46,8 @@ It also packages the [Bitnami PostgreSQL chart](https://github.com/bitnami/chart To install the chart with the release name `my-release`: ```console -$ helm repo add my-repo https://charts.bitnami.com/bitnami -$ helm install my-release my-repo/kubeapps --namespace kubeapps --create-namespace +helm repo add my-repo https://charts.bitnami.com/bitnami +helm install my-release my-repo/kubeapps --namespace kubeapps --create-namespace ``` The command deploys Kubeapps on the Kubernetes cluster in the `kubeapps` namespace. The [Parameters](#parameters) section lists the parameters that can be configured during installation. @@ -64,7 +66,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` | | `global.storageClass` | Global StorageClass for Persistent Volume(s) | `""` | - ### Common parameters | Name | Description | Value | @@ -80,7 +81,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `diagnosticMode.command` | Command to override all containers in the deployment | `["sleep"]` | | `diagnosticMode.args` | Args to override all containers in the deployment | `["infinity"]` | - ### Traffic Exposure Parameters | Name | Description | Value | @@ -100,7 +100,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `ingress.ingressClassName` | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+) | `""` | | `ingress.extraRules` | Additional rules to be covered with this ingress record | `[]` | - ### Kubeapps packaging options | Name | Description | Value | @@ -109,14 +108,13 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `packaging.carvel.enabled` | Enable support for the Carvel (kapp-controller) packaging. | `false` | | `packaging.flux.enabled` | Enable support for Flux (v2) packaging. | `false` | - ### Frontend parameters | Name | Description | Value | | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | ---------------------- | | `frontend.image.registry` | NGINX image registry | `docker.io` | | `frontend.image.repository` | NGINX image repository | `bitnami/nginx` | -| `frontend.image.tag` | NGINX image tag (immutable tags are recommended) | `1.23.3-debian-11-r21` | +| `frontend.image.tag` | NGINX image tag (immutable tags are recommended) | `1.23.3-debian-11-r30` | | `frontend.image.digest` | NGINX image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` | | `frontend.image.pullPolicy` | NGINX image pull policy | `IfNotPresent` | | `frontend.image.pullSecrets` | NGINX image pull secrets | `[]` | @@ -193,7 +191,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `frontend.service.sessionAffinity` | Session Affinity for Kubernetes service, can be "None" or "ClientIP" | `None` | | `frontend.service.sessionAffinityConfig` | Additional settings for the sessionAffinity | `{}` | - ### Dashboard parameters | Name | Description | Value | @@ -274,7 +271,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `dashboard.service.ports.http` | Dashboard service HTTP port | `8080` | | `dashboard.service.annotations` | Additional custom annotations for Dashboard service | `{}` | - ### AppRepository Controller parameters | Name | Description | Value | @@ -342,7 +338,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `apprepository.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `true` | | `apprepository.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` | - ### Auth Proxy parameters | Name | Description | Value | @@ -350,7 +345,7 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `authProxy.enabled` | Specifies whether Kubeapps should configure OAuth login/logout | `false` | | `authProxy.image.registry` | OAuth2 Proxy image registry | `docker.io` | | `authProxy.image.repository` | OAuth2 Proxy image repository | `bitnami/oauth2-proxy` | -| `authProxy.image.tag` | OAuth2 Proxy image tag (immutable tags are recommended) | `7.4.0-debian-11-r35` | +| `authProxy.image.tag` | OAuth2 Proxy image tag (immutable tags are recommended) | `7.4.0-debian-11-r43` | | `authProxy.image.digest` | OAuth2 Proxy image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` | | `authProxy.image.pullPolicy` | OAuth2 Proxy image pull policy | `IfNotPresent` | | `authProxy.image.pullSecrets` | OAuth2 Proxy image pull secrets | `[]` | @@ -383,7 +378,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `authProxy.resources.requests.cpu` | The requested CPU for the OAuth2 Proxy container | `25m` | | `authProxy.resources.requests.memory` | The requested memory for the OAuth2 Proxy container | `32Mi` | - ### Pinniped Proxy parameters | Name | Description | Value | @@ -419,7 +413,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `pinnipedProxy.service.ports.pinnipedProxy` | Pinniped Proxy service port | `3333` | | `pinnipedProxy.service.annotations` | Additional custom annotations for Pinniped Proxy service | `{}` | - ### Other Parameters | Name | Description | Value | @@ -427,7 +420,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `clusters` | List of clusters that Kubeapps can target for deployments | `[]` | | `rbac.create` | Specifies whether RBAC resources should be created | `true` | - ### Feature flags | Name | Description | Value | @@ -437,7 +429,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `featureFlags.operators` | Enable support for Operators in Kubeapps | `false` | | `featureFlags.schemaEditor.enabled` | Enable a visual editor for customizing the package schemas | `false` | - ### Database Parameters | Name | Description | Value | @@ -454,7 +445,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `postgresql.resources.requests.cpu` | The requested CPU for the PostgreSQL container | `250m` | | `postgresql.resources.requests.memory` | The requested memory for the PostgreSQL container | `256Mi` | - ### kubeappsapis parameters | Name | Description | Value | @@ -547,7 +537,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `kubeappsapis.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `true` | | `kubeappsapis.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` | - ### Redis® chart configuration | Name | Description | Value | @@ -564,9 +553,8 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith | `redis.replica.disableCommands` | Array with commands to deactivate on Redis® | `[]` | | `redis.replica.persistence.enabled` | Enable Redis® replica data persistence using PVC | `false` | - ```console -$ helm install kubeapps --namespace kubeapps \ +helm install kubeapps --namespace kubeapps \ --set ingress.enabled=true \ my-repo/kubeapps ``` @@ -576,7 +564,7 @@ The above command enables an Ingress Rule to expose Kubeapps. 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 my-repo/kubeapps +helm install kubeapps --namespace kubeapps -f custom-values.yaml my-repo/kubeapps ``` ## Configuration and installation details @@ -600,7 +588,7 @@ 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 +kubectl get services --namespace kubeapps --watch ``` #### Ingress @@ -660,14 +648,14 @@ 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 +helm repo update ``` Now upgrade Kubeapps: ```console -$ export RELEASE_NAME=kubeapps -$ helm upgrade $RELEASE_NAME my-repo/kubeapps +export RELEASE_NAME=kubeapps +helm upgrade $RELEASE_NAME my-repo/kubeapps ``` If you find issues upgrading Kubeapps, check the [troubleshooting](#error-while-upgrading-the-chart) section. @@ -681,7 +669,7 @@ This major updates the PostgreSQL subchart to its newest major, 12.0.0. [Here](h To uninstall/delete the `kubeapps` deployment: ```console -$ helm uninstall -n kubeapps kubeapps +helm uninstall -n kubeapps kubeapps # Optional: Only if there are no more instances of Kubeapps $ kubectl delete crd apprepositories.kubeapps.com @@ -694,7 +682,7 @@ 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 the remaining completed/failed jobs or any stale resources by deleting the namespace ```console -$ kubectl delete namespace kubeapps +kubectl delete namespace kubeapps ``` ## FAQ @@ -731,7 +719,7 @@ Have a look at the [dashboard documentation](https://github.com/vmware-tanzu/kub The example below will match the URL `http://example.com` to the Kubeapps dashboard. For further configuration, please refer to your specific Ingress configuration docs (e.g., [NGINX](https://github.com/kubernetes/ingress-nginx) or [HAProxy](https://github.com/haproxytech/kubernetes-ingress)). ```console -$ helm install kubeapps my-repo/kubeapps \ +helm install kubeapps my-repo/kubeapps \ --namespace kubeapps \ --set ingress.enabled=true \ --set ingress.hostname=example.com \ @@ -741,7 +729,7 @@ $ helm install kubeapps my-repo/kubeapps \ If you are using LDAP via Dex with OIDC or you are getting an error message like `upstream sent too big header while reading response header from upstream` it means the cookie size is too big and can't be processed by the Ingress Controller. You can work around this problem by setting the following Nginx ingress annotations (look for similar annotations in your preferred Ingress Controller): -``` +```text # rest of the helm install ... command --set ingress.annotations."nginx\.ingress\.kubernetes\.io/proxy-read-timeout"=600 --set ingress.annotations."nginx\.ingress\.kubernetes\.io/proxy-buffer-size"=8k @@ -753,7 +741,7 @@ You can work around this problem by setting the following Nginx ingress annotati You may want to serve Kubeapps with a subpath, for instance `http://example.com/subpath`, you have to set the proper Ingress configuration. If you are using the ingress configuration provided by the Kubeapps chart, you will have to set the `ingress.hostname` and `path` parameters: ```console -$ helm install kubeapps my-repo/kubeapps \ +helm install kubeapps my-repo/kubeapps \ --namespace kubeapps \ --set ingress.enabled=true \ --set ingress.hostname=example.com \ @@ -764,7 +752,7 @@ $ helm install kubeapps my-repo/kubeapps \ Besides, if you are using the OAuth2/OIDC login (more information at the [using an OIDC provider documentation](https://github.com/vmware-tanzu/kubeapps/blob/main/site/content/docs/latest/tutorials/using-an-OIDC-provider.md)), you will need, also, to configure the different URLs: ```console -$ helm install kubeapps my-repo/kubeapps \ +helm install kubeapps my-repo/kubeapps \ --namespace kubeapps \ # ... other OIDC and ingress flags --set authProxy.oauthLoginURI="/subpath/oauth2/login" \ @@ -875,13 +863,13 @@ Error: namespaces "kubeapps" is forbidden: User "system:serviceaccount:kube-syst 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 run the following command: ```console -$ kubectl api-versions +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 my-repo/kubeapps --set rbac.create=false +helm install --name kubeapps --namespace kubeapps my-repo/kubeapps --set rbac.create=false ``` ### Error while upgrading the Chart @@ -889,50 +877,49 @@ $ helm install --name kubeapps --namespace kubeapps my-repo/kubeapps --set rbac. It is possible that when upgrading Kubeapps an error appears. That can be caused by a breaking change in the new chart or because the current chart installation is in an inconsistent state. If you find issues upgrading Kubeapps you can follow these steps: > Note: These steps assume that you have installed Kubeapps in the namespace `kubeapps` using the name `kubeapps`. If that is not the case replace the command with your namespace and/or name. -> Note: If you are upgrading from 2.3.1 see the [following section](#upgrading-to-2-3-1). -> Note: If you are upgrading from 2.3.1 see the [following section](#upgrading-to-2-3-1). -> Note: If you are upgrading from 1.X to 2.X see the [following section](#upgrading-to-2-0). +> Note: If you are upgrading from 2.3.1 see the [following section](#user-content-upgrading-to-231). +> Note: If you are upgrading from 1.X to 2.X see the [following section](#user-content-upgrading-to-20). 1. (Optional) Backup your personal repositories (if you have any): -```console -$ kubectl get apprepository -A -o yaml > .yaml -``` + ```console + kubectl get apprepository -A -o yaml > .yaml + ``` 2. Delete Kubeapps: -```console -$ helm del --purge kubeapps -``` + ```console + helm del --purge kubeapps + ``` 3. (Optional) Delete the App Repositories CRD: -> **Warning**: Do not run this step if you have more than one Kubeapps installation in your cluster. + > **Warning**: Do not run this step if you have more than one Kubeapps installation in your cluster. -```console -$ kubectl delete crd apprepositories.kubeapps.com -``` + ```console + kubectl delete crd apprepositories.kubeapps.com + ``` 4. (Optional) Clean the Kubeapps namespace: -> **Warning**: Do not run this step if you have workloads other than Kubeapps in the `kubeapps` namespace. + > **Warning**: Do not run this step if you have workloads other than Kubeapps in the `kubeapps` namespace. -```console -$ kubectl delete namespace kubeapps -``` + ```console + kubectl delete namespace kubeapps + ``` 5. Install the latest version of Kubeapps (using any custom modifications you need): -```console -$ helm repo update -$ helm install --name kubeapps --namespace kubeapps my-repo/kubeapps -``` + ```console + helm repo update + helm install --name kubeapps --namespace kubeapps my-repo/kubeapps + ``` 6. (Optional) Restore any repositories you backed up in the first step: -```console -$ kubectl apply -f .yaml -``` + ```console + kubectl apply -f .yaml + ``` After that you should be able to access the new version of Kubeapps. If the above doesn't work for you or you run into any other issues please open an [issue](https://github.com/vmware-tanzu/kubeapps/issues/new). @@ -951,21 +938,21 @@ Kubeapps 2.3.1 (Chart version 6.0.0) introduces some breaking changes. Helm-spec 1. Kubeapps will no longer create a database secret for you automatically but rather will rely on the default behavior of the PostgreSQL chart. If you try to upgrade Kubeapps and you installed it without setting a password, you will get the following error: -```console -Error: UPGRADE FAILED: template: kubeapps/templates/NOTES.txt:73:4: executing "kubeapps/templates/NOTES.txt" at : error calling include: template: kubeapps/charts/common/templates/_errors.tpl:18:48: executing "common.errors.upgrade.passwords.empty" at : error calling fail: -PASSWORDS ERROR: you must provide your current passwords when upgrade the release - 'postgresql.postgresqlPassword' must not be empty, please add '--set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD' to the command. To get the current value: -``` + ```console + Error: UPGRADE FAILED: template: kubeapps/templates/NOTES.txt:73:4: executing "kubeapps/templates/NOTES.txt" at : error calling include: template: kubeapps/charts/common/templates/_errors.tpl:18:48: executing "common.errors.upgrade.passwords.empty" at : error calling fail: + PASSWORDS ERROR: you must provide your current passwords when upgrade the release + 'postgresql.postgresqlPassword' must not be empty, please add '--set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD' to the command. To get the current value: + ``` -The error gives you generic instructions for retrieving the PostgreSQL password, but if you have installed a Kubeapps version prior to 2.3.1, the name of the secret will differ. Run the following command: + The error gives you generic instructions for retrieving the PostgreSQL password, but if you have installed a Kubeapps version prior to 2.3.1, the name of the secret will differ. Run the following command: -```console -$ export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace "kubeapps" kubeapps-db -o jsonpath="{.data.postgresql-password}" | base64 -d) -``` + ```console + export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace "kubeapps" kubeapps-db -o jsonpath="{.data.postgresql-password}" | base64 -d) + ``` -> NOTE: Replace the namespace in the command with the namespace in which you have deployed Kubeapps. + > NOTE: Replace the namespace in the command with the namespace in which you have deployed Kubeapps. -Make sure that you have stored the password in the variable `$POSTGRESQL_PASSWORD` before continuing with the next issue. + Make sure that you have stored the password in the variable `$POSTGRESQL_PASSWORD` before continuing with the next issue. 2. The chart `initialRepos` are no longer installed using [Helm hooks](https://helm.sh/docs/topics/charts_hooks/), which caused these repos not to be handled by Helm after the first installation. Now they will be tracked for every update. However, if you do not delete the existing ones, it will fail to update with: @@ -976,7 +963,7 @@ Error: UPGRADE FAILED: rendered manifests contain a resource that already exists To bypass this issue, you will need to before delete all the initialRepos from the chart values (only the `bitnami` repo by default): ```console -$ kubectl delete apprepositories.kubeapps.com -n kubeapps bitnami +kubectl delete apprepositories.kubeapps.com -n kubeapps bitnami ``` > NOTE: Replace the namespace in the command with the namespace in which you have deployed Kubeapps. @@ -986,14 +973,14 @@ After that, you will be able to upgrade Kubeapps to 2.3.1 using the existing dat > **WARNING**: Make sure that the variable `$POSTGRESQL_PASSWORD` is properly populated. Setting a wrong (or empty) password will corrupt the release. ```console -$ helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD +helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD ``` ### Upgrading to 2.0.1 (Chart 5.0.0) [On November 13, 2020, Helm 2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm 3 and to be consistent with the Helm project itself regarding the Helm 2 EOL. -**What changes were introduced in this major version?** +#### What changes were introduced in this major version? - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field. - Move dependency information from the _requirements.yaml_ to the _Chart.yaml_ @@ -1001,7 +988,7 @@ $ helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresql - The different fields present in the _Chart.yaml_ file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts - In the case of PostgreSQL subchart, apart from the same changes that are described in this section, there are also other major changes due to the _master/slave_ nomenclature was replaced by _primary/readReplica_. [Here](https://github.com/bitnami/charts/pull/4385) you can find more information about the changes introduced. -**Considerations when upgrading to this version** +#### Considerations when upgrading to this version - If you want to upgrade to this version using Helm 2, this scenario is not supported as this version does not support Helm 2 anymore - If you installed the previous version with Helm 2 and wants to upgrade to this version with Helm 3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm 2 to 3 @@ -1010,10 +997,10 @@ $ helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresql > Note: The command below assumes that Kubeapps has been deployed in the kubeapps namespace using "kubeapps" as release name, if that is not the case, adapt the command accordingly. ```console -$ kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave +kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave ``` -**Useful links** +#### Useful links - - @@ -1032,7 +1019,7 @@ Due to the last point, it is necessary to run a command before upgrading to Kube > Note: The command below assumes that Kubeapps has been deployed in the kubeapps namespace using "kubeapps" as release name, if that is not the case, adapt the command accordingly. ```console -$ kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave +kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave ``` After that, you should be able to upgrade Kubeapps as always and the database will be repopulated. @@ -1045,10 +1032,10 @@ Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at - http://www.apache.org/licenses/LICENSE-2.0 + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and -limitations under the License. +limitations under the License. \ No newline at end of file diff --git a/chart/kubeapps/values.yaml b/chart/kubeapps/values.yaml index a8b5126258b..20e9247dfb7 100644 --- a/chart/kubeapps/values.yaml +++ b/chart/kubeapps/values.yaml @@ -205,7 +205,7 @@ frontend: image: registry: docker.io repository: bitnami/nginx - tag: 1.23.3-debian-11-r21 + tag: 1.23.3-debian-11-r30 digest: "" ## Specify a imagePullPolicy ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent' @@ -1142,7 +1142,7 @@ authProxy: image: registry: docker.io repository: bitnami/oauth2-proxy - tag: 7.4.0-debian-11-r35 + tag: 7.4.0-debian-11-r43 digest: "" ## Specify a imagePullPolicy ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent' From 2ddb17f080a66447e330198588e9e2fd6751e6ed Mon Sep 17 00:00:00 2001 From: Michael Nelson Date: Thu, 2 Mar 2023 09:47:30 +1100 Subject: [PATCH 2/2] Set dev chart version. Signed-off-by: Michael Nelson --- chart/kubeapps/Chart.yaml | 2 +- chart/kubeapps/README.md | 4 +--- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/chart/kubeapps/Chart.yaml b/chart/kubeapps/Chart.yaml index 3633b4b3781..2ed18672f50 100644 --- a/chart/kubeapps/Chart.yaml +++ b/chart/kubeapps/Chart.yaml @@ -32,4 +32,4 @@ maintainers: name: kubeapps sources: - https://github.com/vmware-tanzu/kubeapps -version: 12.2.6 +version: 12.2.7-dev0 diff --git a/chart/kubeapps/README.md b/chart/kubeapps/README.md index cef8e30ad56..dc372a5b8a2 100644 --- a/chart/kubeapps/README.md +++ b/chart/kubeapps/README.md @@ -1,5 +1,3 @@ - - # Kubeapps packaged by Bitnami Kubeapps is a web-based UI for launching and managing applications on Kubernetes. It allows users to deploy trusted applications and operators to control users access to the cluster. @@ -1038,4 +1036,4 @@ Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and -limitations under the License. \ No newline at end of file +limitations under the License.