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
⚠️ WIP - New API for Security Groups #1751
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: EmilienM The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/uncc tobiasgiese dulek |
This looks like a flexible approach that allows users to implement security groups tailored to their needs. I'm wondering if it makes sense to investigate similar implementations across other providers as well and to mirror their API/naming scheme whereever it makes sense to do so. CAPA, for example, defines a CNIIngressRule resource, which could serve as an inspiration here. In line with their naming scheme we could adopt Either way, thank you for working on this ❤️ |
df38c23
to
0dedf43
Compare
736052f
to
99ab7e0
Compare
99ab7e0
to
713d139
Compare
Note for self when I'm back to it next week: I need to add bastion rules in templates for e2e to pass. |
6c89825
to
fbf1deb
Compare
@EmilienM: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Note: this one is not staled, I'll come back to it at some point this year, now that we have a new API for Security Groups. |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1752
Special notes for your reviewer:
TODOs:
/hold