-
Notifications
You must be signed in to change notification settings - Fork 323
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
Add config for webhook-cert-manager
tolerations
#712
Conversation
Co-authored-by: Kyle Schochenmaier <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great Thomas!!
I think the style of tolerations has varied throughout our values.yaml, with some being set to "" and some being set to null
, but I think since the inconsistency exists already, and this matches one of the patterns, it still works. For example see https://github.com/hashicorp/consul-k8s/blob/main/charts/consul/values.yaml#L885-L895
@ndhanushkodi, I noticed that too. I thought it might be a good onboarding task to pick a standard and I can go through and change all of the nullish instances to use that in a later PR. |
* Add a new flag to the framework, -use-kind. The only thing it affects currently are the mesh gateway tests: it uses NodePort service instead of the LoadBalancer service to expose the mesh gateways. This is because load balancer services are not available on kind. For the NodePort services, we don't need to do anything to allow cross-cluster communication because kind uses the docker bridge network, and so the nodes are reachable by default. * Change the main pipeline to use kind instead of gke, and move gke tests to the nightly pipeline. * Use circleci's parallelism feature to run tests in parallel. Currently, tests are split by package, which is not the best efficient way to parallelize them, but we can address that at a later time. Currently, using 6 parallel nodes reduces the test runtime to about 30min.
* Add webhookCertManager.tolerations setting * Add tolerations to webhook cert template * Add bats test for setting tolerations * Update CHANGELOG * Set PR number in CHANGELOG * Add short desc to webhookCertManager * Update charts/consul/values.yaml Co-authored-by: Kyle Schochenmaier <[email protected]> Co-authored-by: Kyle Schochenmaier <[email protected]>
Changes proposed in this PR:
This work closes issue #655 where the user was running Consul on a private cluster in GKE.
How I've tested this PR:
Added bats and manually produced the deployment YAML using helm.
How I expect reviewers to test this PR:
Run bats
Checklist: