-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport of NET-581 - Added vault namespace in helm into release/1.1.x #2926
Conversation
…xy-default add failover policy to service resolver and proxy default
This reverts commit 2fb7944.
* Terraform: increase node sizes * update GKE to use already created subnets * Dispatch: dispatch to consul-k8s-workflows
* Update status on PRs * Split pr and push into 2 different files so that context can be passed through
* Add a cleanup cron job
* draft of adding sameness group CRD * move sameness group tests to ent test file * update tests * fix lint issues * generate yaml and update helm charts * update field descriptions and validation and its test * remove unwanted files, add license comments back * rename samenessgroups to samenessgroup * fix resource names * update failing unit test
* changes to connhelper, add job lifecycle test * yaml fixes * move around job yaml files, update grace period times * yaml change * timer change * wait for job to start when deploying * fix file paths * Skip Lifecycle Test on t-proxy --------- Co-authored-by: Thomas Eckert <teckert@hashicorp.com>
* change container creation order. Change order of container creation so that envoy container is created before app container. * change tests to fit proxy container added first * add sidecar first iff lifecycle enabled * update tests to include/exclude lifecycle * container ordering in multiport + lifecycle, test case * create changelog * change exec calls to specify container specify containers when exec'ing * Update 2743.txt * small fixes to appending sidecar
* feat: add helm value for consul resource-apis experiment * Apply suggestions from code review Co-authored-by: John Murret <john.murret@hashicorp.com> * PR feedback part 2 --------- Co-authored-by: John Murret <john.murret@hashicorp.com>
…ityContext (#2787) * Add NET_BIND_SERVICE capability to Consul's restricted securityContext * Add changelog entry * Update related bats tests * Change type of release note
* Added tests for partition dns/pq - did some light refactoring
…nnect-CA-via-Helm-Stanza/especially-set-fowl
5c2fbb1
to
91df90c
Compare
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes 15 out of 16 committers have signed the CLA.
Paul Glass seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
Backport
This PR is auto-generated from #2841 to be assessed for backporting due to the inclusion of the label backport/1.1.x.
🚨
The person who merged in the original PR is:
@absolutelightning
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
Changes proposed in this PR:
vaultNamespace
insecretsBackend.vault
invalues.yaml
"{"connect": [{ "ca_config": [{ "namespace": "value"}]}]}"
inconnectCA.additionalConfig
vaultNamespace
is present, it automatically adds annotation below to the templates.How I've tested this PR:
a. CI
b. Updated test
TestVault_VaultNamespace
Test Steps -
Output -
How I expect reviewers to test this PR:
Checklist:
Overview of commits