apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T15:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-40-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-40.ec2.internal uid: fe8a8fbc-4c4e-4fb5-bdd8-2afbc7d6bfa9 resourceVersion: "64605" uid: add8ec61-d874-4f09-a720-f91704295e78 spec: sourcePod: network-check-source-6f78d59f99-nbxc9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T15:46:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.111043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:14:32Z" - latency: 1.271681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:13:32Z" - latency: 1.128563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:12:32Z" - latency: 886.36µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:11:32Z" - latency: 1.001409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:10:32Z" - latency: 1.073332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:09:32Z" - latency: 1.147332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:08:32Z" - latency: 1.176298ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:07:32Z" - latency: 1.157769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:06:32Z" - latency: 1.799954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:05:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T15:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-40-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-40.ec2.internal uid: fe8a8fbc-4c4e-4fb5-bdd8-2afbc7d6bfa9 resourceVersion: "60274" uid: 2d38e9c2-7f0f-4158-8faa-9ee43e95f993 spec: sourcePod: network-check-source-6f78d59f99-nbxc9 targetEndpoint: a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T15:45:32Z" message: 'load-balancer-api-external: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.288696ms message: 'load-balancer-api-external: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:09:32Z" - latency: 7.155245ms message: 'load-balancer-api-external: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:09:32Z" - latency: 18.744908ms message: 'load-balancer-api-external: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:08:32Z" - latency: 10.914557ms message: 'load-balancer-api-external: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:08:32Z" - latency: 18.0731ms message: 'load-balancer-api-external: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:07:32Z" - latency: 7.375913ms message: 'load-balancer-api-external: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:07:32Z" - latency: 33.217524ms message: 'load-balancer-api-external: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:06:32Z" - latency: 6.287301ms message: 'load-balancer-api-external: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:06:32Z" - latency: 17.632779ms message: 'load-balancer-api-external: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:05:32Z" - latency: 9.422863ms message: 'load-balancer-api-external: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:05:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T15:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-40-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-40.ec2.internal uid: fe8a8fbc-4c4e-4fb5-bdd8-2afbc7d6bfa9 resourceVersion: "60275" uid: b31fe3e1-40fa-4eff-8da6-eb6f690f0cd1 spec: sourcePod: network-check-source-6f78d59f99-nbxc9 targetEndpoint: a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T15:45:32Z" message: 'load-balancer-api-internal: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 19.151621ms message: 'load-balancer-api-internal: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:09:32Z" - latency: 7.20686ms message: 'load-balancer-api-internal: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:09:32Z" - latency: 17.828747ms message: 'load-balancer-api-internal: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:08:32Z" - latency: 10.945496ms message: 'load-balancer-api-internal: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:08:32Z" - latency: 21.470689ms message: 'load-balancer-api-internal: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:07:32Z" - latency: 7.405088ms message: 'load-balancer-api-internal: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:07:32Z" - latency: 29.269012ms message: 'load-balancer-api-internal: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:06:32Z" - latency: 6.31832ms message: 'load-balancer-api-internal: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:06:32Z" - latency: 24.794974ms message: 'load-balancer-api-internal: tcp connection to a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:05:32Z" - latency: 9.488645ms message: 'load-balancer-api-internal: resolved host name a147efefe6f1a440e975c96c2e78504d-a54ea740c9871571.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:05:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T15:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-40-to-network-check-target-ip-10-0-129-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-40.ec2.internal uid: fe8a8fbc-4c4e-4fb5-bdd8-2afbc7d6bfa9 resourceVersion: "64602" uid: be92a79e-4441-4c66-8ab7-d067f78d6937 spec: sourcePod: network-check-source-6f78d59f99-nbxc9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T15:46:32Z" message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.34321ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:14:32Z" - latency: 928.304µs message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:13:32Z" - latency: 1.563918ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:12:32Z" - latency: 1.070162ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:11:32Z" - latency: 1.570267ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:10:32Z" - latency: 945.95µs message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:09:32Z" - latency: 1.326693ms message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:08:32Z" - latency: 976.092µs message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:07:32Z" - latency: 958.642µs message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:06:32Z" - latency: 813.1µs message: 'network-check-target-ip-10-0-129-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:05:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T15:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-40-to-network-check-target-ip-10-0-133-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-40.ec2.internal uid: fe8a8fbc-4c4e-4fb5-bdd8-2afbc7d6bfa9 resourceVersion: "64603" uid: 03ac248b-304f-4cd1-b021-a8d1da39b57c spec: sourcePod: network-check-source-6f78d59f99-nbxc9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T15:46:32Z" message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.873117ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:14:32Z" - latency: 2.730133ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:13:32Z" - latency: 2.553136ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:12:32Z" - latency: 2.029297ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:11:32Z" - latency: 2.419804ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:10:32Z" - latency: 2.281628ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:09:32Z" - latency: 2.140374ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:08:32Z" - latency: 2.846561ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:07:32Z" - latency: 2.356834ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:06:32Z" - latency: 2.684782ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:05:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T15:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-40-to-network-check-target-ip-10-0-140-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-40.ec2.internal uid: fe8a8fbc-4c4e-4fb5-bdd8-2afbc7d6bfa9 resourceVersion: "64604" uid: 2034f4d3-6ff0-42ba-9c2e-3706e1c61c33 spec: sourcePod: network-check-source-6f78d59f99-nbxc9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T15:46:32Z" message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.338398ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:14:32Z" - latency: 2.238477ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:13:32Z" - latency: 2.584208ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:12:32Z" - latency: 2.647808ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:11:32Z" - latency: 2.459803ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:10:32Z" - latency: 2.352018ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:09:32Z" - latency: 2.621451ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:08:32Z" - latency: 2.794616ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:07:32Z" - latency: 2.40605ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:06:32Z" - latency: 2.462604ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:05:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T15:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-40-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-40.ec2.internal uid: fe8a8fbc-4c4e-4fb5-bdd8-2afbc7d6bfa9 resourceVersion: "60272" uid: d3a55c90-e681-4dd3-a42d-68c5ff1ba084 spec: sourcePod: network-check-source-6f78d59f99-nbxc9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T15:45:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.13µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:09:32Z" - latency: 1.696044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:09:32Z" - latency: 1.164608ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:08:32Z" - latency: 1.822287ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:08:32Z" - latency: 830.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:07:32Z" - latency: 1.731931ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:07:32Z" - latency: 867.911µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:06:32Z" - latency: 1.783326ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:06:32Z" - latency: 1.030775ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:05:32Z" - latency: 2.44899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:05:32Z" kind: List metadata: resourceVersion: ""