c9a12dd310
* feat: Add support for TXT record encryption This commit introduces support for TXT record encryption in the external-dns Helm chart. The `txtEncrypt` section has been added to the values.yaml file. This section allows enabling TXT record encryption and specifying the AES-256-GCM encryption key or an existing secret name to be used. The templates `_helpers.tpl`, `dep-ds.yaml`, and `secret.yaml` have been modified to include the necessary configuration and environment variables related to TXT record encryption. Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * fix: Correctly indent template call in _helpers.tpl Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * fix: Disable txt encryption by default Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * fix: Encode supplied aesKey as a Base64 string Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Update Chart.yaml Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> * feat: Generate default secret when aesKey and secretName are not set but txtEncryption is enabled Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * feat: Generate default secret when aesKey and secretName are not set but txtEncryption is enabled Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * fix: Remove duplicate docs line Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * fix: Remove duplicate docs line Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * fix: Update version in Chart.yaml to 6.36.0 Signed-off-by: Lukas Jost <lukas.jost@outlook.com> * Bump chart version Signed-off-by: Miguel Ruiz <miruiz@vmware.com> Signed-off-by: Miguel Ruiz <miruiz@vmware.com> --------- Signed-off-by: Lukas Jost <lukas.jost@outlook.com> Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> Signed-off-by: Miguel Ruiz <miruiz@vmware.com> Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com> Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> Co-authored-by: Miguel Ruiz <miruiz@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 Tanzu 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 verifications to ensure the Helm charts work as expected, see the testing strategy defined at TESTING.md.
Before you begin
Prerequisites
- Kubernetes 1.23+
- Helm 3.8.0+
Setup a Kubernetes Cluster
The quickest way to set up a Kubernetes cluster to install Bitnami Charts is by following the "Bitnami Get Started" guides for the different services:
- Get Started with Bitnami Charts using VMware Tanzu Kubernetes Grid (TKG)
- Get Started with Bitnami Charts using VMware Tanzu Mission Control (TMC)
- Get Started With Bitnami Charts Using Azure Marketplace Kubernetes Applications
- 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 © 2024 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.
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.