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.

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

DRAFT: AAW Architecture: Investigate same-cluster isolation of platform level deployments #1989

Open
2 tasks
Souheil-Yazji opened this issue Nov 11, 2024 · 0 comments
Labels
kind/feature New feature or request

Comments

@Souheil-Yazji
Copy link
Contributor

Preface

Currently, our dev cluster provides very little value to us. In-cluster isolation is a huge boon of K8s, maybe we can use that to simply drop the dev cluster by using "Dev" namespaces and label selection logic in the appropriate places.

We'd definitely have to consult Cloud Native Solutions on this approach, but I feel like it's feasible and possibly even better due to the scale of our ops.

Describe the solution you'd like

  • investigate the possiblity of using "dev" labeled namespaces to isolate dev-tiered deployments and prod-tiered deployments.
  • create a map itemizing the scope of changes introduced with such an initiative, this definitely is not trivial. One example is network policy management and profile-controller states.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've
considered.

Additional context

Add any other context or screenshots about the feature request here.

@Souheil-Yazji Souheil-Yazji added the kind/feature New feature or request label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant