deckhouse / deckhouse/deckhouse
[cloud-provider-*] add support for natgw in each zone of multiAZ installations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 162
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 653
Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Use case. Why is this important?
Currently, if we're using WithNAT cluster layout in cloud, all traffic from the cluster goes through the one nat instance only, which is created in some of the availability zones. If any outage happens in AZ with natgw instance, cluster communication with the outer world will be impossible.
Proposed Solution
Adding support of routing table per AZ should help, it would make possible to point default route in particular AZ to particular nat instance, instead of a single default route for all of the availability zones
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the cloud-provider-* implementation for WithNAT cluster layouts and trace how the default route is shared across availability zones; done means each zone has its own routing table and NAT gateway route, with traffic remaining available when one zone fails.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100