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.

Sign up for GitHub

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

Jump to bottom

Allow namespace isolation via network policies #82

Merged
merged 1 commit into from
May 26, 2022
Merged

Allow namespace isolation via network policies #82

merged 1 commit into from
May 26, 2022

Conversation

fbladilo
Copy link
Contributor

@fbladilo fbladilo commented May 26, 2022 •
edited
Loading

  • Implement namespace isolation via network policies, by default feature is turned on. OCP has support for network policies by default in OpenShift SDN , in k8s clusters calico can be installed
  • Policy allows ingress traffic to all ports from any pod that lives in the Tackle namespace, blocks all other ingress traffic
  • Enforcement of policy via immutable namespace label kubernetes.io/metadata.name=
  • If the cluster lacks support for k8s network policies , the policy will not have any effect
  • Bumped minKubeVersion to v1.22.0 for network policy feature compatibility
  • Tested on OCP v4.10 and minikube v1.24 w/ calico

@fbladilo fbladilo requested a review from jortel May 26, 2022 19:05
jortel
jortel approved these changes May 26, 2022
View reviewed changes
Copy link
Contributor

@jortel jortel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fbladilo fbladilo merged commit aba0d70 into konveyor:main May 26, 2022
@jmontleon jmontleon mentioned this pull request Apr 7, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jortel jortel jortel approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@fbladilo @jortel