apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:47:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-197-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-197.us-west-2.compute.internal uid: a0504d99-adef-4c52-ae39-867eaadaf67f resourceVersion: "33626" uid: 07ae0cf2-aaf0-410e-af14-3d85373b62a5 spec: sourcePod: network-check-source-6f78d59f99-r8sp5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T04:54:48Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.942871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:01:48Z" - latency: 1.344244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:00:48Z" - latency: 959.91µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:59:48Z" - latency: 1.641452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:58:48Z" - latency: 997.801µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:57:48Z" - latency: 1.766247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:56:48Z" - latency: 1.186911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:55:48Z" - latency: 1.037056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:54:48Z" - latency: 907.484µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:53:48Z" - latency: 1.218754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:52:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:47:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-197-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-197.us-west-2.compute.internal uid: a0504d99-adef-4c52-ae39-867eaadaf67f resourceVersion: "29458" uid: 8f8ee73b-ed90-450e-80db-69a86c17b3da spec: sourcePod: network-check-source-6f78d59f99-r8sp5 targetEndpoint: afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T04:53:48Z" message: 'load-balancer-api-external: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.09862ms message: 'load-balancer-api-external: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:59:48Z" - latency: 6.937901ms message: 'load-balancer-api-external: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:59:48Z" - latency: 51.194421ms message: 'load-balancer-api-external: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:58:48Z" - latency: 7.236609ms message: 'load-balancer-api-external: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:58:48Z" - latency: 52.868542ms message: 'load-balancer-api-external: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:57:48Z" - latency: 6.632547ms message: 'load-balancer-api-external: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:57:48Z" - latency: 50.106982ms message: 'load-balancer-api-external: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:56:48Z" - latency: 7.211675ms message: 'load-balancer-api-external: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:56:48Z" - latency: 51.614604ms message: 'load-balancer-api-external: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:55:48Z" - latency: 6.666422ms message: 'load-balancer-api-external: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:47:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-197-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-197.us-west-2.compute.internal uid: a0504d99-adef-4c52-ae39-867eaadaf67f resourceVersion: "29457" uid: 6806c971-d9e0-47ec-817a-2c795da31172 spec: sourcePod: network-check-source-6f78d59f99-r8sp5 targetEndpoint: afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T04:53:48Z" message: 'load-balancer-api-internal: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.109581ms message: 'load-balancer-api-internal: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:59:48Z" - latency: 7.025478ms message: 'load-balancer-api-internal: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:59:48Z" - latency: 51.761301ms message: 'load-balancer-api-internal: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:58:48Z" - latency: 7.180736ms message: 'load-balancer-api-internal: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:58:48Z" - latency: 50.03064ms message: 'load-balancer-api-internal: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:57:48Z" - latency: 6.737116ms message: 'load-balancer-api-internal: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:57:48Z" - latency: 56.035708ms message: 'load-balancer-api-internal: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:56:48Z" - latency: 7.337303ms message: 'load-balancer-api-internal: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:56:48Z" - latency: 56.246982ms message: 'load-balancer-api-internal: tcp connection to afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:55:48Z" - latency: 6.719136ms message: 'load-balancer-api-internal: resolved host name afa22c3b1a41d46a3a14deb84ca41375-9501ff5f8f77d258.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T04:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:47:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-197-to-network-check-target-ip-10-0-132-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-197.us-west-2.compute.internal uid: a0504d99-adef-4c52-ae39-867eaadaf67f resourceVersion: "33618" uid: db71bc8f-398e-45f0-a5cb-5149c78d5787 spec: sourcePod: network-check-source-6f78d59f99-r8sp5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:54:48Z" message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.281561ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:01:48Z" - latency: 1.040421ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:00:48Z" - latency: 817.974µs message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:59:48Z" - latency: 963.277µs message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:58:48Z" - latency: 849.521µs message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:57:48Z" - latency: 1.191962ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:56:48Z" - latency: 946.093µs message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:55:48Z" - latency: 908.11µs message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:54:48Z" - latency: 1.054834ms message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:53:48Z" - latency: 861.234µs message: 'network-check-target-ip-10-0-132-197: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:52:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:47:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-197-to-network-check-target-ip-10-0-134-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-197.us-west-2.compute.internal uid: a0504d99-adef-4c52-ae39-867eaadaf67f resourceVersion: "33617" uid: 981cb153-e1e7-4f40-bdb3-6469eb043f22 spec: sourcePod: network-check-source-6f78d59f99-r8sp5 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:54:48Z" message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.179599ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:01:48Z" - latency: 2.297862ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:00:48Z" - latency: 2.018942ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:59:48Z" - latency: 2.207619ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:58:48Z" - latency: 1.921866ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:57:48Z" - latency: 2.163233ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:56:48Z" - latency: 1.767406ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:55:48Z" - latency: 1.963607ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:54:48Z" - latency: 1.614795ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:53:48Z" - latency: 1.933955ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:52:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:47:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-197-to-network-check-target-ip-10-0-140-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-197.us-west-2.compute.internal uid: a0504d99-adef-4c52-ae39-867eaadaf67f resourceVersion: "33620" uid: a13f0579-41a1-4c1a-9ba2-4ea8a3d7a7f9 spec: sourcePod: network-check-source-6f78d59f99-r8sp5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T04:54:48Z" message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.652277ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:01:48Z" - latency: 2.503631ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:00:48Z" - latency: 2.311847ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:59:48Z" - latency: 2.440093ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:58:48Z" - latency: 1.896034ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:57:48Z" - latency: 3.656615ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:56:48Z" - latency: 2.371476ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:55:48Z" - latency: 2.187862ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:54:48Z" - latency: 2.294173ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:53:48Z" - latency: 2.533916ms message: 'network-check-target-ip-10-0-140-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:52:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T04:47:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-197-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-197.us-west-2.compute.internal uid: a0504d99-adef-4c52-ae39-867eaadaf67f resourceVersion: "29456" uid: 1a3a70a5-083a-4e1e-a753-2e9b7bec9de3 spec: sourcePod: network-check-source-6f78d59f99-r8sp5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T04:53:48Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 860.13µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:59:48Z" - latency: 1.830104ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:59:48Z" - latency: 1.08052ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:58:48Z" - latency: 2.57738ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:58:48Z" - latency: 825.487µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:57:48Z" - latency: 1.814025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:57:48Z" - latency: 951.833µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:56:48Z" - latency: 2.251216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:56:48Z" - latency: 940.586µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T04:55:48Z" - latency: 2.036048ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T04:55:48Z" kind: List metadata: resourceVersion: ""