-
Notifications
You must be signed in to change notification settings - Fork 178
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: set a default policy group name #1094
base: master
Are you sure you want to change the base?
Conversation
build PR |
1 similar comment
build PR |
build pr |
This also maps k8s namespace to EPG Signed-off-by: Ranjith <[email protected]>
k8s-test: first_master_make_targets:=run-build | ||
k8s-test: export VAGRANT_CWD:=$(PWD)/vagrant/k8s | ||
k8s-test: export CONTIV_K8S_USE_KUBEADM:=1 CONTIV_NODES:=3 PYTHONIOENCODING:=utf-8 | ||
k8s-test: k8s-cluster make-on-first-master-dep |
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.
Will these duplicate targets be combined into a single k8s-test
?
// Pods need to be in a group to allow policies to be applied after pod | ||
// creation, if a group is not specified by the user, then place pod | ||
// into a group shared across the pod's namespace, as contiv group is part | ||
// of a network and network is in a k8s namespace |
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.
Can you add the above four lines in the description of this PR so that reviewers know what it does. Also, curious to know if this approach decreased the runtime of system tests? If so, by how much?
Pods that did not specify a contiv group will be
assigned a default based on a name pattern:
"ns-" + + "-default"