mirror of
https://github.com/gravitational/teleport.git
synced 2026-10-24 02:25:42 +08:00
d2a656ef3f
* Allow for probe timeouts to be configurable When setting up a new Teleport enterprise cluster on GCP, I noticed that I needed to set the probe timeouts to get the cluster to be healthy. This seems to be a known issue (https://github.com/kubernetes/kubernetes/issues/89898). As a "stopgap", I've updated the helm chart to allow for end users to be able to configure these timeouts. * Update configuration option name and add documentation * Update docs/pages/kubernetes-access/helm/reference.mdx Co-authored-by: Gus Luxton <gus@goteleport.com> * Add tests for probeTimeoutSeconds * Add probeTimeoutSeconds to required values * Add probeTimeoutSeconds to teleport-kube-agent * Add tests for probeTimeoutSeconds to teleport-kube-agent * Add probeTimeoutSeconds to teleport-kube-agent reference Co-authored-by: Hunter Madison <hunter.madison@instana.com> Co-authored-by: Hunter Madison <hmadison@users.noreply.github.com>
Unit tests for Helm charts
Helm chart unit tests run here using the helm3-unittest Helm plugin.
If you get a snapshot error during your testing, you should verify that your changes intended to alter the output, then run this command from the root of your Teleport checkout to update the snapshots:
make -C build.assets test-helm-update-snapshots
After this, re-run the tests to make sure everything is fine:
make -C build.assets test-helm
Commit the updated snapshots along with your changes.