8d539d5d21
* [bitnami/apache] Make `ingress.tls` into a bool Its contents were not parsed anyway since chart version [v9.0.0](https://github.com/bitnami/charts/pull/7491/), so this change has no functional effect. Signed-off-by: Andreas Lindhé <andreas@lindhe.io> * [bitnami/apache] Cleanup messy ingress.tls logic I have convinced myself that this change has no functional effect. * `ingress.tls` always had to be set, so that logic is the same. * It is now possible to set `ingress.tls` without setting `ingress.certManager` or `ingress.selfSigned`. What's the harm in that? Perhaps someone would like to provide a TLS secret manually... Signed-off-by: Andreas Lindhé <andreas@lindhe.io> * [bitnami/apache] Remove unused value ingress.hosts Signed-off-by: Andreas Lindhé <andreas@lindhe.io> * [bitnami/apache] Bump chart version Signed-off-by: Andreas Lindhé <andreas@lindhe.io> * [bitnami/apache] Remove ingress.certManager This change removes the long deprecated annotation for cert-manager from the Ingress resource. NOTE: Technically, this is a breaking change. If someone is using the `ingress.certManager` value, they will lose the annotation. I imagine there are few cases where the annotation has any effect, but there's always someone out there running some really odd configuration... It's of course still possible to have the annotation, it just has to be included in `ingress.annotations`, along with the rest of the annotations. Since the value is no longer in use anywhere, we also remove it from values.yaml. Signed-off-by: Andreas Lindhé <andreas@lindhe.io> * [bitnami/apache] Bump chart version Signed-off-by: Andreas Lindhé <andreas@lindhe.io> * [bitnami/apache] Revert breaking change by checking ingress.selfSigned Before this change, I had accidentally missed the case where the user has `--set 'ingress.enabled=true,ingress.selfSigned=true'`, which inadvertently introduced a breaking change. This change makes sure this case is covered as before the PR was merged. Signed-off-by: Andreas Lindhé <andreas@lindhe.io> * Full standardization of ingress Signed-off-by: Andrés Bono <andresbono@vmware.com> --------- Signed-off-by: Andreas Lindhé <andreas@lindhe.io> Signed-off-by: Andrés Bono <andresbono@vmware.com> Co-authored-by: Andrés Bono <andresbono@vmware.com>
The Bitnami Library for Kubernetes
Popular applications, provided by Bitnami, ready to launch on Kubernetes using Kubernetes Helm.
Looking to use our applications in production? Try VMware Application Catalog, the enterprise edition of Bitnami Application Catalog.
TL;DR
helm install my-release oci://registry-1.docker.io/bitnamicharts/<chart>
Vulnerabilities scanner
Each Helm chart contains one or more containers. Those containers use images provided by Bitnami through its test & release pipeline and whose source code can be found at bitnami/containers.
As part of the container releases, the images are scanned for vulnerabilities, here you can find more info about this topic.
Since the container image is an immutable artifact that is already analyzed, as part of the Helm chart release process we are not looking for vulnerabilities in the containers but running different verification to ensure the Helm charts work as expected, see the testing strategy defined at TESTING.md.
Before you begin
Prerequisites
- Kubernetes 1.19+
- Helm 3.2.0+
Setup a Kubernetes Cluster
The quickest way to setup a Kubernetes cluster to install Bitnami Charts is following the "Bitnami Get Started" guides for the different services:
- Get Started with Bitnami Charts using VMware Tanzu Kubernetes Grid
- Get Started with Bitnami Charts using VMware Tanzu Mission Control
- Get Started with Bitnami Charts using the Azure Kubernetes Service (AKS)
- Get Started with Bitnami Charts using the Amazon Elastic Container Service for Kubernetes (EKS)
- Get Started with Bitnami Charts using the Google Kubernetes Engine (GKE)
For setting up Kubernetes on other cloud platforms or bare-metal servers refer to the Kubernetes getting started guide.
Install Helm
Helm is a tool for managing Kubernetes charts. Charts are packages of pre-configured Kubernetes resources.
To install Helm, refer to the Helm install guide and ensure that the helm binary is in the PATH of your shell.
Using Helm
Once you have installed the Helm client, you can deploy a Bitnami Helm Chart into a Kubernetes cluster.
Please refer to the Quick Start guide if you wish to get running in just a few commands, otherwise the Using Helm Guide provides detailed instructions on how to use the Helm client to manage packages on your Kubernetes cluster.
Useful Helm Client Commands:
- Install a chart:
helm install my-release oci://registry-1.docker.io/bitnamicharts/<chart> - Upgrade your application:
helm upgrade my-release oci://registry-1.docker.io/bitnamicharts/<chart>
License
Copyright © 2023 VMware, Inc.
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.