-
Notifications
You must be signed in to change notification settings - Fork 53
Changes to enable IPSEC Network Configuration #395
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
Conversation
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.
Hi @suman-jainkeri thank you for your PR. Pls see my comment about cluster-network-03-config.yml file.
@suman-jainkeri Thank you for the PR. Pls see my comments. Thank you. |
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.
Hi @suman-jainkeri Thank you. The PR looks good.
@suman-jainkeri Pls fix the DCO and pls do a rebase to enable merge. |
Signed-off-by: suman-jainkeri <[email protected]>
Signed-off-by: suman-jainkeri <[email protected]>
Updated the retries to 40 for all pods to be in Running State in Hosted Control Plane Namespace. --------- Signed-off-by: root <[email protected]> Co-authored-by: root <[email protected]> Co-authored-by: root <[email protected]> Signed-off-by: suman-jainkeri <[email protected]>
Signed-off-by: suman-jainkeri <[email protected]>
Signed-off-by: suman-jainkeri <[email protected]>
I verified IPSec with configuring ipsec mode as Full. Briefly, Full mode is to encrypt pod-to-pod traffic and, optionally, traffic to external hosts. Cluster came up and verified if IPSEC is enabled [root@t313lp32 ~]# oc -n openshift-ovn-kubernetes rsh ovnkube-node-2vgkm ovn-nbctl --no-leader-only get nb_global . ipsec Defaulted container "ovn-controller" out of: ovn-controller, ovn-acl-logging, kube-rbac-proxy-node, kube-rbac-proxy-ovn-metrics, northd, nbdb, sbdb, ovnkube-controller, kubecfg-setup (init) true From above output it's evident that IPSec is enabled. With the above verification procedure, you can verify that IPsec is enabled between pods on your cluster when IPsec is configured in Full mode. Signed-off-by: suman-jainkeri <[email protected]>
Signed-off-by: suman-jainkeri <[email protected]>
Signed-off-by: suman-jainkeri <[email protected]>
Signed-off-by: suman-jainkeri <[email protected]>
Signed-off-by: suman-jainkeri <[email protected]>
This PR handles the changes to enable IPSEC Network Config changes during the installation.