Cluster configurations may include mutating admission controllers which
dynamically add security contexts to pods and containers.
OpenShift uses this pattern to implement required uid ranges that
differ on a per-namespace basis, and OpenShift's security admission
plugin rejects any pods that make runAsUser requests outside of that
valid uid range.
Removing the securityContext field from the Jenkins pod spec allows the
OpenShift security admission plugin to assign a uid in the correct
range to each container in the pod on behalf of the user, avoiding the
need to provide helm with a different runAsUser value for each
namespace in which Jenkins is deployed.
* Fix namespace documentation
The current state of the documentation doesnt work (issue #6153) instead --namespace=kafka should be used to deploy kafka in kafka namespace
* fix last commit
The current state of the documentation doesnt work (issue #6153) instead --namespace=kafka should be used to deploy kafka in kafka namespace
* Update Chart.yaml
* Bug fix: Add if condition to configurtion mounting section, and mention the dependecy on kube-state-metrics.
* Increment chart version to 0.1.1
* Incrmented the chart version number
* Fixed image configuration in README for the prometheus-cloudwatch-exporter.
* Bumped version of prometheys-cloudwatch-exporter.
* Bumped the correct version for prometheus-cloudwatch-exporter.
* Add ELK chart
* Add needed templates directory
* Rename elk to elastic-stack
Fix versions in requirements
Add initial NOTES.txt
* Add option to disable curator and nginx-ldapauth-proxy
* Add _helpers.tpl and fix NOTES.txt
* Remove NOTES.txt file and helpers
Add christian-roggia as a maintainer
* Disable nginx-ldapauth-proxy and curator by default
Add missing _helpers.tpl
* Add Chart icon and appVersion
* Update version of Logstash
Add option to disable logstash
* Add optional FluentD sub-chart
Update versions of other sub-charts
* Switch to incubator/elasticsearch-curator chart
* Update requirements.lock
* Switch nginx-ldapauth-proxy to stable repo
Update dependencies
* Add home page for elastic-stack
* Add OWNERS file for elastic-stack
* Update elasticsearch, kibana and logstash versions
* Update lock file after adjusting requirements
* Update helpers.tpl
* Add README for elastic-stack
* Add config example for nginx-ldapauth-proxy
* Add basic NOTES for elastic-stack
* Use the right values for kibana service type
* Update minimun Kube version
* Starting work on the Vault Operator
Get us some chart-y goodness!
* Starting work on the Vault Operator
Get us some chart-y goodness!
* Vault operator chart lints
Time to see if it works?
* Vault operators deploys!
Need to test on a real k8s instance, now
* Starting work on the Vault Operator
Get us some chart-y goodness!
* Vault operator chart lints
Time to see if it works?
* Vault operators deploys!
Need to test on a real k8s instance, now
* Don't set the etcd-operator to cluster-wide
Cuz that'd be bad, mmkay?
* Validated to be awesome!
Last step is to update docs
* Updated README with all of the values
* Updated values
Things noticed while documenting them
* Syncing up with the 2.8+ Helm chart style
* Fix indentation issue
* Updating as per code review
* Migrate the `vault-operator` to `stable`
* Replace references to incubator with stable
* added cloud sql proxy container
* Add cloud sql proxy
* make changes on stable/drone
* update for general usage [stable/drone]
* Bump minor version for new feature
* adds service annotations; adds extralabels to components; canonicalizes template naming; adds values-defined existingSecret
* updates README with test.enabled value description
* sets container ports with values
* updates approvers and reviewers
* removes OWNERS file
* deployment container to using hard-coded port values
* fixes pv command in README
* bumps openldap container version to 1.2.1
The default value has to be an empty string instead of an empty map because
it is passed to the 'tpl' function. Otherwise Helm gives you a warning when the chart is
installed and 'keycloak.extraEnv' is used.
* [stable/datadog] Allow skipping Secret creation
* [stable/datadog] Update description of Secret creation in NOTES and README
* [stable/datadog] Use `.Values.existingSecret` instead of `.Values.secret.create` in order to skip API key secret creation and read from the provided one
* [stable/datadog] Bump version to 0.18.0
* [stable/datadog] Use `.Values.datadog.apiKeyExistingSecret` instead of `.Values.existingSecret`
* [stable/datadog] Rename API secret name template from `apiSecretName` to `datadog.apiSecretName`
* [stable/datadog] Update README to properly explain how to override API key secret
* Add support for AWS Secrets Manager
* Rename credentialManager.secretsmanager to credentialManager.awsSecretsManager
* Bump minor version for new feature
Jacob LeGrone
Sandeep Mendiratta
Hermain
Taehyun Kim
AdamDang
danigrmartinez
Shubham Jain
Kevin Lefevre
Tim Jespers
Yahav Biran
David J. M. Karlsen
tmestdagh
Pete Brown
Will Newby
Sasha
Michael Laccetti
mihirat
Ricardo Hernandez
Jody McIntyre
Giancarlo Rubio
Alexander Babai
Erik Madrid
Krzysztof Nazarewski
Juan Ariza Toledano
Bitnami Bot
Chris Hiestand
Maxime Guyot
Sergey Nuzhdin
Reinhard Nägele
Guilherme Garnier
Adrien Chardon
Jeff Hastings
Hidetake Iwata
jakemccloskey
Timur Khafizov
Kurt McAlpine