mirror of
https://github.com/bitnami/charts.git
synced 2026-03-14 06:47:28 +08:00
[bitnami/*] Make Helm charts 100% OCI (#15998)
* [bitnami/*] Make Helm charts 100% OCI Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> * Add main files and scaffolding Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> * Bump chart version Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> * Improve helm upgrade instruction Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> * Revert bitnami/common version bump Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> * Prettify Chart.yamls Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> * Regenerate Chart.lock and bump chart versions Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> --------- Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
This commit is contained in:
Carlos Rodríguez Hernández
committed by
GitHub
GitHub
parent
4596ed932f
commit
884151035e
@@ -1,12 +1,12 @@
|
||||
dependencies:
|
||||
- name: redis
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
version: 17.9.5
|
||||
- name: postgresql
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
version: 12.2.8
|
||||
- name: common
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
version: 2.2.4
|
||||
digest: sha256:45a084bb283f15756f75735e72d91a1b5ea31f437025dcaba5e9538f1ff14cf1
|
||||
generated: "2023-04-20T05:10:29.951567734Z"
|
||||
digest: sha256:338f8dd541bfc32ea3a472a2d3aa5251bcf9dcb4f5a12abf136c8d4b009874b1
|
||||
generated: "2023-04-20T09:33:25.255469+02:00"
|
||||
|
||||
@@ -6,14 +6,14 @@ appVersion: 2.7.0
|
||||
dependencies:
|
||||
- condition: packaging.flux.enabled
|
||||
name: redis
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
version: 17.x.x
|
||||
- condition: packaging.helm.enabled
|
||||
name: postgresql
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
version: 12.x.x
|
||||
- name: common
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
tags:
|
||||
- bitnami-common
|
||||
version: 2.x.x
|
||||
@@ -32,4 +32,4 @@ maintainers:
|
||||
name: kubeapps
|
||||
sources:
|
||||
- https://github.com/vmware-tanzu/kubeapps
|
||||
version: 12.2.10
|
||||
version: 12.3.0
|
||||
|
||||
@@ -9,8 +9,7 @@ Kubeapps is a web-based UI for launching and managing applications on Kubernetes
|
||||
## 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 install my-release oci://registry-1.docker.io/bitnamicharts/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 +43,7 @@ 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 install my-release oci://registry-1.docker.io/bitnamicharts/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.
|
||||
@@ -554,7 +552,7 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
|
||||
```console
|
||||
helm install kubeapps --namespace kubeapps \
|
||||
--set ingress.enabled=true \
|
||||
my-repo/kubeapps
|
||||
oci://registry-1.docker.io/bitnamicharts/kubeapps
|
||||
```
|
||||
|
||||
The above command enables an Ingress Rule to expose Kubeapps.
|
||||
@@ -562,7 +560,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 oci://registry-1.docker.io/bitnamicharts/kubeapps
|
||||
```
|
||||
|
||||
## Configuration and installation details
|
||||
@@ -653,7 +651,7 @@ Now upgrade Kubeapps:
|
||||
|
||||
```console
|
||||
export RELEASE_NAME=kubeapps
|
||||
helm upgrade $RELEASE_NAME my-repo/kubeapps
|
||||
helm upgrade $RELEASE_NAME oci://registry-1.docker.io/bitnamicharts/kubeapps
|
||||
```
|
||||
|
||||
If you find issues upgrading Kubeapps, check the [troubleshooting](#error-while-upgrading-the-chart) section.
|
||||
@@ -717,7 +715,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 oci://registry-1.docker.io/bitnamicharts/kubeapps \
|
||||
--namespace kubeapps \
|
||||
--set ingress.enabled=true \
|
||||
--set ingress.hostname=example.com \
|
||||
@@ -739,7 +737,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 oci://registry-1.docker.io/bitnamicharts/kubeapps \
|
||||
--namespace kubeapps \
|
||||
--set ingress.enabled=true \
|
||||
--set ingress.hostname=example.com \
|
||||
@@ -750,7 +748,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 oci://registry-1.docker.io/bitnamicharts/kubeapps \
|
||||
--namespace kubeapps \
|
||||
# ... other OIDC and ingress flags
|
||||
--set authProxy.oauthLoginURI="/subpath/oauth2/login" \
|
||||
@@ -867,7 +865,7 @@ 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 oci://registry-1.docker.io/bitnamicharts/kubeapps --set rbac.create=false
|
||||
```
|
||||
|
||||
### Error while upgrading the Chart
|
||||
@@ -910,7 +908,7 @@ It is possible that when upgrading Kubeapps an error appears. That can be caused
|
||||
|
||||
```console
|
||||
helm repo update
|
||||
helm install --name kubeapps --namespace kubeapps my-repo/kubeapps
|
||||
helm install --name kubeapps --namespace kubeapps oci://registry-1.docker.io/bitnamicharts/kubeapps
|
||||
```
|
||||
|
||||
6. (Optional) Restore any repositories you backed up in the first step:
|
||||
@@ -971,7 +969,7 @@ 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 oci://registry-1.docker.io/bitnamicharts/kubeapps -n kubeapps --set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD
|
||||
```
|
||||
|
||||
### Upgrading to 2.0.1 (Chart 5.0.0)
|
||||
|
||||
Reference in New Issue
Block a user