* allow existing claims in master and data
* version bump requested by linter
* wrong version
* silly me, does need a bump
* version changes
* requested fixes
* documentation
* Fix wrong referenced values in init-cluster.yaml and update-cluster.yaml
In the templates, .Values.cluster.initTimeout was used instead of .Values.cluster.activeDeadlineSeconds
* Run init-cluster job without helm hooks using new parameters .cluster.helmHooks
* Update README.md with .cluster.helmHooks parameter
* Add "release/revision" annotation to init-cluster job so that it is ran for each revision
* Make job name unique for each revision if no hooks are specified
* Remove un-needed cluster.helmHooks
Co-authored-by: Maxence Boutet <maxenceboutet@oulook.com>
* 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>
