Add cloud-specific deployment instructions

[manibh-kong]

Recently I had a task to install Kuma in EKS cluster. I noticed that whether I have multi zone or standalone setup there are steps that are missing or hard to find in documentation.
For example, in Amazon EKS installation one has to make sure to install following:
1- Kuma DNS: to resolve the virtual IPs
2- Kong Ingress controller: it can be misleading, one may try to use Kuma Ingress, but that's only for the cross zone communication and for Kuma internals and can not be used as ingress controller. Thus we should install Kong Ingress (DB Less) otherwise after enabling MTLS all Amazon NLB's will fail due to mTLS cert checking for SAN of NLB...
3- For multi zone setup, Kuma Ingress is also required.
4- Ingress resource sample / template that will be required in this case to allow traffic from outside of EKS cluster to micro services.
I can contribute to create the initial draft of what needs to be installed / configured with some syntax.

[nickolaev]

We have started an effort to gather this information for the Multi-zone setup here:
#402

[github-actions]

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

[lahabana]

#402 is old enough to have to be redone.

[github-actions]

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

[lahabana]

Worth keeping this issue in mind when tackling this: #614

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[lahabana]

Do we still have anything cloud specific?

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[slonka]

@lahabana I recently came across this - #1232

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[lahabana]

Duplicate of: #1847 which has more info