From ccdafa96f627bdb09e3a29a5fccb7c47478a0996 Mon Sep 17 00:00:00 2001 From: Ingo Richtsmeier Date: Thu, 12 Dec 2024 10:53:07 +0100 Subject: [PATCH] More explicit description how to apply the DNS changes (#4747) * More explicit description how to apply the DNS changes * tech writer edits --------- Co-authored-by: Cole Garbo Co-authored-by: Mark Sellings --- .../self-managed/setup/deploy/amazon/amazon-eks/dual-region.md | 3 ++- .../self-managed/setup/deploy/amazon/amazon-eks/dual-region.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md b/docs/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md index 68aa8a6c4d9..137adb9efe3 100644 --- a/docs/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md +++ b/docs/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md @@ -233,7 +233,8 @@ kubectl --context $CLUSTER_1 apply -f https://raw.githubusercontent.com/camunda/ ``` 3. The script will retrieve the IPs of the load balancer via the AWS CLI and return the required config change. -4. As the script suggests, copy the statement between the placeholders to edit the CoreDNS configmap in cluster 0 and cluster 1, depending on the placeholder. +4. The script prints the `kubectl edit` commands to change the DNS settings of each cluster inline. Copy the statement between the placeholders to edit the CoreDNS configmap in cluster 0 and cluster 1, depending on the placeholder. + An alternative to inline editing is to create two copies of the file `kubernetes/coredns.yml`, one for each cluster. Add the section generated by the script to each file. Apply the changes to each cluster with e.g. `kubectl --context cluster-london -n kube-system apply -f file.yml`. Replace the `context` parameter with your current values.
Example output diff --git a/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md b/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md index 49af2c274ab..15670e7721b 100644 --- a/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md +++ b/versioned_docs/version-8.6/self-managed/setup/deploy/amazon/amazon-eks/dual-region.md @@ -233,7 +233,8 @@ kubectl --context $CLUSTER_1 apply -f https://raw.githubusercontent.com/camunda/ ``` 3. The script will retrieve the IPs of the load balancer via the AWS CLI and return the required config change. -4. As the script suggests, copy the statement between the placeholders to edit the CoreDNS configmap in cluster 0 and cluster 1, depending on the placeholder. +4. The script prints the `kubectl edit` commands to change the DNS settings of each cluster inline. Copy the statement between the placeholders to edit the CoreDNS configmap in cluster 0 and cluster 1, depending on the placeholder. + An alternative to inline editing is to create two copies of the file `kubernetes/coredns.yml`, one for each cluster. Add the section generated by the script to each file. Apply the changes to each cluster with e.g. `kubectl --context cluster-london -n kube-system apply -f file.yml`. Replace the `context` parameter with your current values.
Example output