More explicit description how to apply the DNS changes

[ingorichtsmeier]

Description

Clarify the change DNS procedure for the AWS dual region setup.

I stumbled about this when setting up my own dual region cluster. The description how to apply the changes was hidden in the output of the script.

It's not everybody favor to do inline Kubernetes object editing using VI, so I added an alternative with editiing the files locally and ally them with kubectl afterwards.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[Langleu]

Thanks for the addition 🚀.
Looks good from my side as an alternative approach.

[ingorichtsmeier]

Thank you, @conceptualshark, for improving my language.

Could you please take over to merge and publish with one of the next docs release?

It looks like a single button to push, But I don't know if you need any more labels or other actions behind the scene.

[mesellings]

Merged for you, will be released in the next docs release 👍