[DNM] Configure ovnkube-node and ovn-ipsec for IPsec Child SA metric#3036
[DNM] Configure ovnkube-node and ovn-ipsec for IPsec Child SA metric#3036pperiyasamy wants to merge 2 commits into
Conversation
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughThe PR adds IPsec enablement to OVN-Kubernetes node components: the startup script conditionally passes ChangesOVN IPsec enablement across node components
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pperiyasamy The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/testwith openshift/cluster-network-operator/master/e2e-ovn-ipsec-step-registry openshift/ovn-kubernetes#3259 |
Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
4227e6c to
e56f3b8
Compare
|
@pperiyasamy: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Created custom test suite for validating IPsec Child SA state metrics from ovn-kubernetes PR openshift#3259 and CNO PR openshift#3036. Test: ipsec-metrics-250nodes - Scale to 250 worker nodes (m5.xlarge) - Run control-plane tests - Run data-path tests - Run IPsec metrics validation: * Verify ovnkube_controller_ipsec_tunnel_ike_child_sa_state metric exists * Check metric labels (node, remote_ip, local_ip) * Validate IPsec tunnel states (INSTALLED, REKEYED, etc) * Run 250×250 pod-to-pod connectivity matrix test ConfigMap Integration: - Test script reads registry URL from ConfigMap (ipsec-registry-config in ci namespace) - No config file edits needed - just create ConfigMap and trigger test - Helper script: ~/Devel/ipsec-2025/set-registry-url.sh <registry-url> Workflow: - openshift-qe-installer-aws-ovn-ipsec (cluster + infra setup) - openshift-qe-workers-scale (scales to 250 nodes) - openshift-qe-control-plane (control plane validation) - openshift-qe-data-path-tests (network/ingress tests) - openshift-qe-ipsec-metrics-validation (custom IPsec validation) Trigger: /test ipsec-metrics-250nodes Future: 500-node test commented out, will enable after 250-node is stable Related: - openshift/ovn-kubernetes#3259 - openshift/cluster-network-operator#3036 - CORENET-5852
Created custom test suite for validating IPsec Child SA state metrics from ovn-kubernetes PR openshift#3259 and CNO PR openshift#3036. Test: ipsec-metrics-250nodes - Scale to 250 worker nodes (m5.xlarge) - Run control-plane tests - Run data-path tests - Run IPsec metrics validation: * Verify ovnkube_controller_ipsec_tunnel_ike_child_sa_state metric exists * Check metric labels (node, remote_ip, local_ip) * Validate IPsec tunnel states (INSTALLED, REKEYED, etc) * Run 250×250 pod-to-pod connectivity matrix test ConfigMap Integration: - Test script reads registry URL from ConfigMap (ipsec-registry-config in ci namespace) - No config file edits needed - just create ConfigMap and trigger test - Helper script: ~/Devel/ipsec-2025/set-registry-url.sh <registry-url> Workflow: - openshift-qe-installer-aws-ovn-ipsec (cluster + infra setup) - openshift-qe-workers-scale (scales to 250 nodes) - openshift-qe-control-plane (control plane validation) - openshift-qe-data-path-tests (network/ingress tests) - openshift-qe-ipsec-metrics-validation (custom IPsec validation) Trigger: /test ipsec-metrics-250nodes Future: 500-node test commented out, will enable after 250-node is stable Related: - openshift/ovn-kubernetes#3259 - openshift/cluster-network-operator#3036 - CORENET-5852
Registry: registry.build07.ci.openshift.org/ci-ln-kh2v56k/release:latest This commit sets CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE to test the IPsec Child SA state metric from: - openshift/ovn-kubernetes#3259 - openshift/cluster-network-operator#3036
Created custom test suite for validating IPsec Child SA state metrics from ovn-kubernetes PR openshift#3259 and CNO PR openshift#3036. Test: ipsec-metrics-250nodes - Scale to 250 worker nodes (m5.xlarge) - Run control-plane tests - Run data-path tests - Run IPsec metrics validation: * Verify ovnkube_controller_ipsec_tunnel_ike_child_sa_state metric exists * Check metric labels (node, remote_ip, local_ip) * Validate IPsec tunnel states (INSTALLED, REKEYED, etc) * Run 250×250 pod-to-pod connectivity matrix test ConfigMap Integration: - Test script reads registry URL from ConfigMap (ipsec-registry-config in ci namespace) - No config file edits needed - just create ConfigMap and trigger test - Helper script: ~/Devel/ipsec-2025/set-registry-url.sh <registry-url> Workflow: - openshift-qe-installer-aws-ovn-ipsec (cluster + infra setup) - openshift-qe-workers-scale (scales to 250 nodes) - openshift-qe-control-plane (control plane validation) - openshift-qe-data-path-tests (network/ingress tests) - openshift-qe-ipsec-metrics-validation (custom IPsec validation) Trigger: /test ipsec-metrics-250nodes Future: 500-node test commented out, will enable after 250-node is stable Related: - openshift/ovn-kubernetes#3259 - openshift/cluster-network-operator#3036 - CORENET-5852
Registry: registry.build07.ci.openshift.org/ci-ln-kh2v56k/release:latest This commit sets CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE to test the IPsec Child SA state metric from: - openshift/ovn-kubernetes#3259 - openshift/cluster-network-operator#3036
Created custom test suite for validating IPsec Child SA state metrics from ovn-kubernetes PR openshift#3259 and CNO PR openshift#3036. Test: ipsec-metrics-250nodes - Scale to 250 worker nodes (m5.xlarge) - Run control-plane tests - Run data-path tests - Run IPsec metrics validation: * Verify ovnkube_controller_ipsec_tunnel_ike_child_sa_state metric exists * Check metric labels (node, remote_ip, local_ip) * Validate IPsec tunnel states (INSTALLED, REKEYED, etc) * Run 250×250 pod-to-pod connectivity matrix test ConfigMap Integration: - Test script reads registry URL from ConfigMap (ipsec-registry-config in ci namespace) - No config file edits needed - just create ConfigMap and trigger test - Helper script: ~/Devel/ipsec-2025/set-registry-url.sh <registry-url> Workflow: - openshift-qe-installer-aws-ovn-ipsec (cluster + infra setup) - openshift-qe-workers-scale (scales to 250 nodes) - openshift-qe-control-plane (control plane validation) - openshift-qe-data-path-tests (network/ingress tests) - openshift-qe-ipsec-metrics-validation (custom IPsec validation) Trigger: /test ipsec-metrics-250nodes Future: 500-node test commented out, will enable after 250-node is stable Related: - openshift/ovn-kubernetes#3259 - openshift/cluster-network-operator#3036 - CORENET-5852
Registry: registry.build07.ci.openshift.org/ci-ln-kh2v56k/release:latest This commit sets CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE to test the IPsec Child SA state metric from: - openshift/ovn-kubernetes#3259 - openshift/cluster-network-operator#3036
cc @SachinNinganure
Summary by CodeRabbit