Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add cloud-specific deployment instructions #405

Closed
manibh-kong opened this issue Mar 31, 2021 · 15 comments
Closed

Add cloud-specific deployment instructions #405

manibh-kong opened this issue Mar 31, 2021 · 15 comments
Labels
kind/improvement Improvement on an existing feature triage/duplicated already exists

Comments

@manibh-kong
Copy link

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
Copy link

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

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 2, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2021

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 lahabana added kind/improvement Improvement on an existing feature triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/stale Inactive for some time. It will be triaged again labels Dec 6, 2021
@lahabana
Copy link
Contributor

lahabana commented Dec 6, 2021

#402 is old enough to have to be redone.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jan 6, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2022

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
Copy link
Contributor

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

@michaelbeaumont michaelbeaumont changed the title Add EKS/ AKS Architectural overview on what needs to be installed/configure Add cloud-specific deployment instructions Jul 26, 2022
@michaelbeaumont michaelbeaumont removed the triage/stale Inactive for some time. It will be triaged again label Jul 26, 2022
@github-actions
Copy link
Contributor

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 github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Oct 25, 2022
@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Oct 25, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jan 24, 2023
@github-actions
Copy link
Contributor

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 lahabana removed the triage/stale Inactive for some time. It will be triaged again label Jan 24, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Apr 25, 2023
@github-actions
Copy link
Contributor

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 lahabana removed the triage/stale Inactive for some time. It will be triaged again label Apr 25, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jul 25, 2023
@github-actions
Copy link
Contributor

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 lahabana removed the triage/stale Inactive for some time. It will be triaged again label Jul 25, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Oct 24, 2023
@github-actions
Copy link
Contributor

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 lahabana removed the triage/stale Inactive for some time. It will be triaged again label Nov 2, 2023
@lahabana
Copy link
Contributor

lahabana commented Nov 2, 2023

Do we still have anything cloud specific?

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 1, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 1, 2024

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
Copy link
Contributor

slonka commented Feb 7, 2024

@lahabana I recently came across this - #1232

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Feb 7, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented May 8, 2024

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 github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 8, 2024
@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label May 20, 2024
@lahabana
Copy link
Contributor

Duplicate of: #1847 which has more info

@lahabana lahabana closed this as not planned Won't fix, can't repro, duplicate, stale Jul 30, 2024
@lahabana lahabana added triage/duplicated already exists and removed triage/accepted The issue was reviewed and is complete enough to start working on it labels Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/improvement Improvement on an existing feature triage/duplicated already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@lahabana @nickolaev @michaelbeaumont @slonka @lukidzi @manibh-kong