apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:16:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-217-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-217.ec2.internal uid: 62284ebf-a6f2-4e86-9810-b66b9f470fad resourceVersion: "53194" uid: 16883b90-b0b0-47f6-b855-54f798c8a2d5 spec: sourcePod: network-check-source-685456655f-pxdwb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T17:23:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.659µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:44:04Z" - latency: 937.176µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:43:04Z" - latency: 1.387759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:42:04Z" - latency: 1.014527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:41:04Z" - latency: 1.021434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:40:04Z" - latency: 1.266831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:39:04Z" - latency: 1.442947ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:38:04Z" - latency: 1.829979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:37:04Z" - latency: 1.446482ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:36:04Z" - latency: 1.439149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:35:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:16:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-217-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-217.ec2.internal uid: 62284ebf-a6f2-4e86-9810-b66b9f470fad resourceVersion: "54918" uid: 60d66d6f-aa39-43b6-b085-67df509a8c4f spec: sourcePod: network-check-source-685456655f-pxdwb targetEndpoint: aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T17:22:04Z" message: 'load-balancer-api-external: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.54563ms message: 'load-balancer-api-external: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:46:04Z" - latency: 8.013592ms message: 'load-balancer-api-external: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:46:04Z" - latency: 4.666374ms message: 'load-balancer-api-external: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:45:04Z" - latency: 8.061462ms message: 'load-balancer-api-external: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:45:04Z" - latency: 5.143207ms message: 'load-balancer-api-external: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:44:04Z" - latency: 9.40621ms message: 'load-balancer-api-external: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:44:04Z" - latency: 4.64444ms message: 'load-balancer-api-external: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:43:04Z" - latency: 8.065692ms message: 'load-balancer-api-external: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:43:04Z" - latency: 5.023355ms message: 'load-balancer-api-external: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:42:04Z" - latency: 8.683678ms message: 'load-balancer-api-external: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:42:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:16:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-217-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-217.ec2.internal uid: 62284ebf-a6f2-4e86-9810-b66b9f470fad resourceVersion: "54917" uid: 92563e41-6608-4fcc-8414-9f032ae4ffcf spec: sourcePod: network-check-source-685456655f-pxdwb targetEndpoint: aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T17:22:04Z" message: 'load-balancer-api-internal: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.51262ms message: 'load-balancer-api-internal: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:46:04Z" - latency: 8.036153ms message: 'load-balancer-api-internal: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:46:04Z" - latency: 4.679517ms message: 'load-balancer-api-internal: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:45:04Z" - latency: 8.030093ms message: 'load-balancer-api-internal: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:45:04Z" - latency: 2.858262ms message: 'load-balancer-api-internal: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:44:04Z" - latency: 9.387321ms message: 'load-balancer-api-internal: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:44:04Z" - latency: 4.141081ms message: 'load-balancer-api-internal: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:43:04Z" - latency: 7.987076ms message: 'load-balancer-api-internal: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:43:04Z" - latency: 3.790621ms message: 'load-balancer-api-internal: tcp connection to aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:42:04Z" - latency: 8.714958ms message: 'load-balancer-api-internal: resolved host name aedd09b818c6346b18f4f0636432aa2b-f0beb2a6c1aff66d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T17:42:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:16:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-217-to-network-check-target-ip-10-0-137-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-217.ec2.internal uid: 62284ebf-a6f2-4e86-9810-b66b9f470fad resourceVersion: "53192" uid: 0c11aad0-8985-47e2-aa9c-155553340790 spec: sourcePod: network-check-source-685456655f-pxdwb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T17:23:04Z" message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.016055ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:44:04Z" - latency: 1.717151ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:43:04Z" - latency: 2.068001ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:42:04Z" - latency: 1.77568ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:41:04Z" - latency: 2.117229ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:40:04Z" - latency: 2.165013ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:39:04Z" - latency: 1.997666ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:38:04Z" - latency: 2.169853ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:37:04Z" - latency: 2.361969ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:36:04Z" - latency: 2.310592ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:35:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:16:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-217-to-network-check-target-ip-10-0-137-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-217.ec2.internal uid: 62284ebf-a6f2-4e86-9810-b66b9f470fad resourceVersion: "53191" uid: 2629d794-2db1-4007-acd4-03371df56210 spec: sourcePod: network-check-source-685456655f-pxdwb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T17:23:04Z" message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 819.923µs message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:44:04Z" - latency: 928.286µs message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:43:04Z" - latency: 963.982µs message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:42:04Z" - latency: 936.033µs message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:41:04Z" - latency: 938.005µs message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:40:04Z" - latency: 1.536133ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:39:04Z" - latency: 1.00099ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:38:04Z" - latency: 1.459708ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:37:04Z" - latency: 955.255µs message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:36:04Z" - latency: 1.056921ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:35:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:16:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-217-to-network-check-target-ip-10-0-140-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-217.ec2.internal uid: 62284ebf-a6f2-4e86-9810-b66b9f470fad resourceVersion: "53193" uid: 1ea7698f-b6e6-46b2-aa70-cd812c51ae97 spec: sourcePod: network-check-source-685456655f-pxdwb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T17:23:04Z" message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.257221ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:44:04Z" - latency: 2.161842ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:43:04Z" - latency: 2.36556ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:42:04Z" - latency: 2.069683ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:41:04Z" - latency: 2.125391ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:40:04Z" - latency: 2.553074ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:39:04Z" - latency: 2.414073ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:38:04Z" - latency: 2.753773ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:37:04Z" - latency: 2.865613ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:36:04Z" - latency: 3.070342ms message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:35:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T17:16:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-217-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-217.ec2.internal uid: 62284ebf-a6f2-4e86-9810-b66b9f470fad resourceVersion: "54916" uid: bbdd2a1e-8525-458d-923e-939e3e6e4a93 spec: sourcePod: network-check-source-685456655f-pxdwb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T17:22:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.001691ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:46:04Z" - latency: 2.020597ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T17:46:04Z" - latency: 1.008331ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:45:04Z" - latency: 1.968549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T17:45:04Z" - latency: 867.57µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:44:04Z" - latency: 2.312273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T17:44:04Z" - latency: 926.449µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:43:04Z" - latency: 1.833911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T17:43:04Z" - latency: 833.529µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T17:42:04Z" - latency: 1.754546ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T17:42:04Z" kind: List metadata: resourceVersion: ""