spelling fixes for examples (#45148)

Co-authored-by: Steven Martin <[email protected]>
This commit is contained in:
Steven Martin
2024-08-06 16:56:08 +00:00
committed by GitHub
co-authored by Steven Martin
parent 0ad5b4e21b
commit 8ffbb39aa8
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -53,7 +53,7 @@ variable "workgroup_max_scanned_bytes_per_query" {
# search events API to prevent increasing costs in case of aggressive use of API.
# In current version Athena Audit logger is not prepared for polling of API.
# Burst=20, time=1m and amount=5, means that you can do 20 requests without any
# throtling, next requests will be thottled, and tokens will be filled to
# throttling, next requests will be throttled, and tokens will be filled to
# rate limit bucket at amount 5 every 1m.
variable "search_event_limiter_burst" {
description = "Number of tokens available for rate limit used on top of search event API"
@@ -2,7 +2,7 @@
and creates them if needed. It also adds common labels, like any other
Helm-deployed resource.
We cannot rely on the "crds/" Helm directory as Helm's startegy is "fire and forget".
We cannot rely on the "crds/" Helm directory as Helm's strategy is "fire and forget".
We have no way to update the CRDs after the initial deployment. As Teleport keeps
adding new field to existing CRs, we need a deployment strategy that supports
updating CRDs.
+1 -1
View File
@@ -287,7 +287,7 @@ global:
clusterDomain: cluster.local
# Labels is a map of key-value pairs about this cluster. Those labels are used
# in Teleport to access the Kuebrnetes cluster. They must not be confused with
# in Teleport to access the Kubernetes cluster. They must not be confused with
# `extraLabels` which are additional labels to add on Kubernetes resources
# created by the Helm chart.
labels: {}