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

Clarify Brupop's port requirements #406

Closed
stockholmux opened this issue Jan 31, 2024 · 1 comment
Closed

Clarify Brupop's port requirements #406

stockholmux opened this issue Jan 31, 2024 · 1 comment

Comments

@stockholmux
Copy link
Member

Discussed in bottlerocket-os/bottlerocket#3600

Originally posted by landbaychrisburrell November 16, 2023
Hi

My understanding is that most of the interactions between the operator and the BottleRocket OS happen by updating the Shadow resources - as such, there is presumably zero ports required to be open - and so locking down the namespace with a policy that prevents all comms for pods into the operator's namespace would be fine?

@stockholmux stockholmux transferred this issue from bottlerocket-os/bottlerocket Jan 31, 2024
@stockholmux
Copy link
Member Author

closed by #419

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant