chore(deps): update docs from repo source

Signed-off-by: kumahq[bot] <110050114+kumahq[bot]@users.noreply.github.com>
kumahq · Dec 4, 2023 · 1efac0b · 1efac0b
1 parent 609a37e
commit 1efac0b
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 0 deletions.
diff --git a/app/docs/dev/helm-values.yaml b/app/docs/dev/helm-values.yaml
@@ -383,6 +383,8 @@ cni:
     runAsGroup: 0
 
 dataPlane:
+  # -- If true, then turn on CoreDNS query logging
+  dnsLogging: false
   image:
     # -- The Kuma DP image repository
     repository: "kuma-dp"

diff --git a/app/docs/dev/kuma-cp.yaml b/app/docs/dev/kuma-cp.yaml
@@ -348,6 +348,8 @@ runtime:
         enabled: true # ENV: KUMA_RUNTIME_KUBERNETES_INJECTOR_BUILTIN_DNS_ENABLED
         # Redirect port for DNS
         port: 15053 # ENV: KUMA_RUNTIME_KUBERNETES_INJECTOR_BUILTIN_DNS_PORT
+        # Enable coredns query logging if true
+        logging: false # ENV: KUMA_RUNTIME_KUBERNETES_INJECTOR_BUILTIN_DNS_LOGGING
       # EBPF defines configuration for the ebpf, when transparent proxy is marked to be
       # installed using ebpf instead of iptables
       ebpf:

diff --git a/app/docs/raw/UPGRADE.md b/app/docs/raw/UPGRADE.md
@@ -6,6 +6,18 @@ with `x.y.z` being the version you are planning to upgrade to.
 If such a section does not exist, the upgrade you want to perform
 does not have any particular instructions.
 
+## Upgrade to `2.6.x`
+
+### Unifying Default Connection Timeout Values
+
+To simplify configuration and provide a more consistent user experience, we've unified the default connection timeout values. When no `MeshTimeout` or `Timeout` policy is specified, the connection timeout will now be the same as the default `connectTimeout` values for `MeshTimeout` and `Timeout` policies. This value is now `5s`, which is a decrease from the previous default of `10s`.
+
+The connection timeout specifies the amount of time Envoy will wait for an upstream TCP connection to be established.
+
+The only users who need to take action are those who are explicitly relying on the previous default connection timeout value of `10s`. These users will need to create a new `MeshTimeout` policy with the appropriate `connectTimeout` value to maintain their desired behavior.
+
+We encourage all users to review their configuration, but we do not anticipate that this change will require any action for most users.
+
 ## Upgrade to `2.5.x`
 
 ### Transparent-proxy and CNI v1 removal