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
[ST] Re-enable applying of NetworkPolicies during namespace creation #9656
Conversation
Signed-off-by: Lukas Kral <lukywill16@gmail.com>
Signed-off-by: Lukas Kral <lukywill16@gmail.com>
/packit test --labels regression |
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp list |
/azp run namespace-rbac-scope-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks 👍
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
Test failures in TF are not related to my PR, they are being fixed in #9649 and then in another PR |
Type of change
Description
During work on
NamespaceManager
I found out that the NetworkPolicies, that were part of the Namespace creation, are not created at all -> theNetworkPolicyTemplates.applyDefaultNetworkPolicy()
method, even though named as "apply", just returned the NetworkPolicy object, which was then never actually created (only inOauthAbstractST
, where it's done byResourceManager
from the beginning).This PR fixes this issue. It adds the correct deployment of NetworkPolicies to
NamespaceManager
, so it is on one place and removes it from anywhere else. Also, it removes old and not used methods after changes, that were made in last PRs.Checklist