aws / aws/aws-eks-best-practices

Confusion with subnet guidance

Open
#335 3 comments 0 reactions 1 assignee View on GitHub

@sheetaljoshi is already working on this.

Since Jun 27, 2023.

correction
Dominant language
Python
Stars
2.2k
Forks
567
Avg merge
6d 6h
Merged PRs (30d)
3

Description

Describe the problem

Feedback received:

  • "what is the implication doing this ? The doc just mentions this one line and no other details. Customer is running their cluster which is sharing the subnets but has not faced any issues yet. Wants to understand if there's anything underlying."
  • "I've not heard this recommendation before and I don't know where it comes from. I disagree with it; there's no compelling need to separate the subnets this way in most cases"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.