-
Notifications
You must be signed in to change notification settings - Fork 159
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
Allow forwarding of all traffic inside the Kubernetes network #3919
Conversation
For Longhorn and other pods to function properly on the Kubernetes "cni0" network, we should allow: - all DNS traffic - forwarding from pods to services - forwarding between pods But we may need to adjust these rules later as we continue developing the Kubernetes clustering support... Signed-off-by: Milan Lenco <milan@zededa.com>
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
@naiming-zededa can you find some device in orangeCorp which is not used by the Jenkins runs and/or figure out how to have Eden run with a kubevirt image so we can get some regression testing in place for kubevirt?
@eriknordmark I will look into the eden integration with the kubevirt |
@naiming-zededa This works for me to run kubevirt-EVE under eden (just change eve.tag for your locally built EVE):
|
Cool. thanks Milan. |
I am testing this on kubevirt eve. Will let you know in 30 mins |
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.
This fix works cf4b1766-574b-4974-bfac-be568107225c:/# kubectl get pods -n longhorn-system |
The yetus complaints are about unmodified code in pkg/pillar/types so ignoring those. |
For Longhorn and other pods to function properly on the Kubernetes "cni0" network, we should allow:
But we may need to adjust these rules later as we continue developing the Kubernetes clustering support...