* Added antiflake pipeline Signed-off-by: alukic <alukic@vmware.com> * Diversified the pipeline Signed-off-by: alukic <alukic@vmware.com> * Make a change to trigger TKG Signed-off-by: alukic <alukic@vmware.com> * Replaced FIPS with normal AKS Signed-off-by: alukic <alukic@vmware.com> * Added extra workflow for Grafana Loki Signed-off-by: alukic <alukic@vmware.com> * Changed the pipeline Signed-off-by: alukic <alukic@vmware.com> * Modified the workflow Signed-off-by: alukic <alukic@vmware.com> * Removed Grafana Loki Signed-off-by: alukic <alukic@vmware.com> * Added the publish and verify pipelines Signed-off-by: alukic <alukic@vmware.com> * Added Cypress tests Signed-off-by: alukic <alukic@vmware.com> * Add one Goss tests Signed-off-by: alukic <alukic@vmware.com> * Trigger VIB Signed-off-by: alukic <alukic@vmware.com> * Change workload value Signed-off-by: alukic <alukic@vmware.com> * Add more Goss tests Signed-off-by: alukic <alukic@vmware.com> * Added the host settings just in case Signed-off-by: alukic <alukic@vmware.com> * Removed the host settings Signed-off-by: alukic <alukic@vmware.com> * Modified the pipeline to add .my to the domain Signed-off-by: alukic <alukic@vmware.com> * Added target IP instead of the hardcoded value Signed-off-by: alukic <alukic@vmware.com> * Added one more Goss test Signed-off-by: alukic <alukic@vmware.com> * Modify the group for the Goss file Signed-off-by: alukic <alukic@vmware.com> * Undo VIB changes and remove test files Signed-off-by: alukic <alukic@vmware.com> * Delete antiflake Signed-off-by: alukic <alukic@vmware.com> * Using fixtures Signed-off-by: alukic <alukic@vmware.com> * Test data change Signed-off-by: alukic <alukic@vmware.com> * Added a change to trigger VIB Signed-off-by: alukic <alukic@vmware.com> * Remove extra params Signed-off-by: alukic <alukic@vmware.com> * Updated the version and changed the readme Signed-off-by: alukic <alukic@vmware.com> * Apply CR suggestions Signed-off-by: alukic <alukic@vmware.com> * Applied CR suggestions Signed-off-by: alukic <alukic@vmware.com> * Made changes as per PR review Signed-off-by: alukic <alukic@vmware.com> * Replaced IP with parameter Signed-off-by: alukic <alukic@vmware.com> * Changed plural values to singular Signed-off-by: alukic <alukic@vmware.com> * Change the Goss file Signed-off-by: alukic <alukic@vmware.com> * Change the Goss test Signed-off-by: alukic <alukic@vmware.com> * Change IP Signed-off-by: alukic <alukic@vmware.com> * Removed extra changes Signed-off-by: alukic <alukic@vmware.com> * Improved the tests Signed-off-by: alukic <alukic@vmware.com> * Replaced hardcoded IP Signed-off-by: alukic <alukic@vmware.com>
The Bitnami Library for Kubernetes
Popular applications, provided by Bitnami, ready to launch on Kubernetes using Kubernetes Helm.
TL;DR
$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm search repo bitnami
$ helm install my-release bitnami/<chart>
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)
- Get Started with Bitnami Charts using the IBM Cloud Kubernetes Service (IKS)
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.
Add Repo
The following command allows you to download and install all the charts from this repository:
$ helm repo add bitnami https://charts.bitnami.com/bitnami
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:
- View available charts:
helm search repo - Install a chart:
helm install my-release bitnami/<package-name> - Upgrade your application:
helm upgrade
License
Copyright © 2022 Bitnami
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.
