bfcac2f558
* [bitnami/opensearch] Fix node-role guards checking autoscaling There are guards around Kubernetes resources specific to nodes differentiated by OpenSearch roles. These guards check whether particular role is enabled. We have implemented these guards, so they check at least if autoscaling is enabled or if replica count is greater than zero. However, we support both horizontal pod autoscaler (HPA) and vertical pod autoscaler (VPA). Our Helm chart values have no unspecified autoscaling. We change guards to check if HPA is enabled. If it is enabled (and other conditions are true), we should configure Kubernetes resources associated with particular role. This is because pods for this particular role will be created as needed. We do not care about VPA, because VPA requires some pods to exists in the first place and we already cover that (or fix in this commit). Signed-off-by: Filip Zrůst <filip.zrust@sinsir.net> * [bitnami/opensearch] Fix guards for OpenSearch Dashboards We already declare Helm chart value to enable or disable OpenSearch Dashboards. We also use guards checking similar and other values for other types of workloads. We use these guards to ultimately decide if particular workloads and Kubernetes resources associated with them should be configured. What we have been missing is a similar guard which checks if OpenSearch Dashboards should be configured. We fix this by introducing opensearch.dashboards.enabled helper template definition. It is similar to opensearch.ingest.enabled because Helm chart values configuring ingest contain “enabled” field as well as fields all the guards check: autoscaling.hpa.enabled and replicaCount. We implement equivalent condition for the new helper template definition. We also apply this new guard consistently with other types of workloads… Signed-off-by: Filip Zrůst <filip.zrust@sinsir.net> * [bitnami/opensearch] Bump version after OpenSearch Dashboards fix Signed-off-by: Filip Zrůst <filip.zrust@sinsir.net> --------- Signed-off-by: Filip Zrůst <filip.zrust@sinsir.net> Signed-off-by: Ibone González Mauraza <gibone@vmware.com> Co-authored-by: Ibone González Mauraza <gibone@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.