5493b53a9f
* discourse helm chart Signed-off-by: Paul Czarkowski <username.taken@gmail.com> * Udpate readme following bitnami best-practices * Remove .gitignore * Use requirements.yaml to support helm2 * Update LICENSE Signed-off-by: Paul Czarkowski <username.taken@gmail.com> * Update bitnami/discourse/Chart.yaml Co-authored-by: Javier J. Salmerón-García <jsalmeron@vmware.com> * Update bitnami/discourse/Chart.yaml Co-authored-by: Javier J. Salmerón-García <jsalmeron@vmware.com> * Update bitnami/discourse/Chart.yaml Co-authored-by: Javier J. Salmerón-García <jsalmeron@vmware.com> * Update bitnami/discourse/Chart.yaml Co-authored-by: Javier J. Salmerón-García <jsalmeron@vmware.com> * Update bitnami/discourse/values.yaml Co-authored-by: Javier J. Salmerón-García <jsalmeron@vmware.com> * Update bitnami/discourse/templates/deployment-sidekiq.yaml Co-authored-by: Javier J. Salmerón-García <jsalmeron@vmware.com> * Work on latest bitnami change requests Signed-off-by: Luca Prete <preteluca@gmail.com> * Fix email indent and add Luca as maintainer * Fix: put back original wordpress chart content * Update bitnami/discourse/Chart.yaml * Update bitnami/discourse/values.yaml * Major lint fixes and intro of external DB and notes * Delete wordpress file * Restore original wordpress deployment file Found unreleated file in the commit, restoring the original * Fix linter identation issues in requirements * Integration of Sidekiq as sidecar This commit includes a lot of new features and refactoring: - Improved helper template functions to retrieve values of variables - Env. variables had been reduced to the actual used ones (i.e. PostgreSQL creation related env vars are not necessary due to the existance of the subchart) - Integration of both Discourse and Sidekiq containers into the same pod - Inclusion of PVC to persist values - Configurable liveness and readiness probes - Identation issues were fixed - NOTES.txt improved - NodeIP as the standard Service type and LoadBalancer for production - README with detailed explanation - Secrets purged to only use needed values - Values-production added - Other more general improvements * Fix linter issues * Chart api version downgraded to v1 * Added special values for CI testing purposes * Fix identation issues * Fix sidekiq liveness probe + increase time * Remove CT targeted files As this Chart was removed from the CT GitHub system. Liveness Probe timing for production values was also updated. * Add Ingress TLS support * Set LoadBalancer service as default one * Add minor improvements to templates I * Fix wrong helper function name * Add loadBalancerIP missing value * Standardize securityContext names to [pod/container]SecurityContext * Add support for optional liveness and readiness probes in sidekiq * Add improvements II * Capabilities for extraVolumes and extraVolumeMounts * Configurable commands for both containers * Add label and annotations at pod level * Add support for common annotations in every resource * Support for custom readiness and liveness probes * Add improvements III * Add commonLabels for all deployed resources * Massive update on README.md * Add comment on both values * Add warning comments in NOTES.txt * Apply formatting to both values files * Update licesing Co-authored-by: Luca Prete <preteluca@gmail.com> Co-authored-by: Javier J. Salmerón-García <jsalmeron@vmware.com> Co-authored-by: Javier J. Salmerón-García <jsalmeron@bitnami.com> Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> Co-authored-by: joancafom <jcarmona@bitnami.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
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 Enterprise PKS
- 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 (c) 2020 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.