apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:42:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.us-east-2.compute.internal uid: f4052499-1e42-4c56-aa2f-f1e16388a44a resourceVersion: "96856" uid: a2803e90-9372-41ef-9196-a0c237fbf760 spec: sourcePod: network-check-source-6f78d59f99-nffwz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T20:49:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.284003ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:24:22Z" - latency: 1.870159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:22Z" - latency: 1.138582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:22Z" - latency: 1.752421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:22Z" - latency: 1.505465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:22Z" - latency: 1.143657ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:22Z" - latency: 1.041451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:22Z" - latency: 1.39354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:22Z" - latency: 869.658µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:16:22Z" - latency: 1.10404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:15:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:42:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.us-east-2.compute.internal uid: f4052499-1e42-4c56-aa2f-f1e16388a44a resourceVersion: "96858" uid: 5ab29c18-19e2-4e8b-9605-53627eddd9b9 spec: sourcePod: network-check-source-6f78d59f99-nffwz targetEndpoint: a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T20:48:22Z" message: 'load-balancer-api-external: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.25055ms message: 'load-balancer-api-external: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:24:22Z" - latency: 8.074759ms message: 'load-balancer-api-external: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:24:22Z" - latency: 3.970631ms message: 'load-balancer-api-external: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:22Z" - latency: 7.233323ms message: 'load-balancer-api-external: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:23:22Z" - latency: 4.788476ms message: 'load-balancer-api-external: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:22Z" - latency: 6.875822ms message: 'load-balancer-api-external: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:22:22Z" - latency: 5.985869ms message: 'load-balancer-api-external: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:22Z" - latency: 7.314739ms message: 'load-balancer-api-external: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:21:22Z" - latency: 6.239249ms message: 'load-balancer-api-external: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:22Z" - latency: 7.226916ms message: 'load-balancer-api-external: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:20:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:42:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.us-east-2.compute.internal uid: f4052499-1e42-4c56-aa2f-f1e16388a44a resourceVersion: "96859" uid: 57119a57-ffcf-438e-87e4-da3d167ff168 spec: sourcePod: network-check-source-6f78d59f99-nffwz targetEndpoint: a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T20:48:22Z" message: 'load-balancer-api-internal: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.760902ms message: 'load-balancer-api-internal: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:24:22Z" - latency: 8.121257ms message: 'load-balancer-api-internal: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:24:22Z" - latency: 4.665273ms message: 'load-balancer-api-internal: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:22Z" - latency: 7.292375ms message: 'load-balancer-api-internal: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:23:22Z" - latency: 4.825086ms message: 'load-balancer-api-internal: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:22Z" - latency: 6.91191ms message: 'load-balancer-api-internal: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:22:22Z" - latency: 7.595465ms message: 'load-balancer-api-internal: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:22Z" - latency: 7.288991ms message: 'load-balancer-api-internal: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:21:22Z" - latency: 3.336082359s message: 'load-balancer-api-internal: tcp connection to a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:22Z" - latency: 7.199285ms message: 'load-balancer-api-internal: resolved host name a4a717949abc448c8a02afb6e419aa30-2e7845090fc158ce.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:20:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:42:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-network-check-target-ip-10-0-133-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.us-east-2.compute.internal uid: f4052499-1e42-4c56-aa2f-f1e16388a44a resourceVersion: "96854" uid: 8d9e813a-dcf2-4683-9829-4ad0d98d98ce spec: sourcePod: network-check-source-6f78d59f99-nffwz targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T20:49:22Z" message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.496263ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:24:22Z" - latency: 2.373158ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:22Z" - latency: 2.189082ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:22Z" - latency: 2.34639ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:22Z" - latency: 2.253644ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:22Z" - latency: 2.52152ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:22Z" - latency: 2.535104ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:22Z" - latency: 2.355811ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:22Z" - latency: 1.950425ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:16:22Z" - latency: 2.300038ms message: 'network-check-target-ip-10-0-133-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:15:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:42:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-network-check-target-ip-10-0-135-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.us-east-2.compute.internal uid: f4052499-1e42-4c56-aa2f-f1e16388a44a resourceVersion: "96852" uid: 19693dac-7412-45c8-9d0c-6c1cbdd26be8 spec: sourcePod: network-check-source-6f78d59f99-nffwz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T20:49:22Z" message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088281ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:24:22Z" - latency: 1.332261ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:22Z" - latency: 1.178459ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:22Z" - latency: 1.067942ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:22Z" - latency: 1.914532ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:22Z" - latency: 1.23284ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:22Z" - latency: 1.52723ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:22Z" - latency: 1.007293ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:22Z" - latency: 1.602148ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:16:22Z" - latency: 1.335072ms message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:15:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:42:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-network-check-target-ip-10-0-141-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.us-east-2.compute.internal uid: f4052499-1e42-4c56-aa2f-f1e16388a44a resourceVersion: "96853" uid: a51982d1-418b-4a04-b034-e2bcbc1149af spec: sourcePod: network-check-source-6f78d59f99-nffwz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T20:49:22Z" message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.109919ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:24:22Z" - latency: 2.649752ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:22Z" - latency: 2.371191ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:22Z" - latency: 5.05665ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:22Z" - latency: 2.45784ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:22Z" - latency: 2.585056ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:22Z" - latency: 2.205465ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:22Z" - latency: 2.054261ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:22Z" - latency: 2.017146ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:16:22Z" - latency: 2.754432ms message: 'network-check-target-ip-10-0-141-65: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:15:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:42:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-104.us-east-2.compute.internal uid: f4052499-1e42-4c56-aa2f-f1e16388a44a resourceVersion: "96855" uid: b4d3d836-6848-446c-b856-fe2462fba3c6 spec: sourcePod: network-check-source-6f78d59f99-nffwz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T20:48:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 985.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:24:22Z" - latency: 2.904342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:24:22Z" - latency: 1.175832ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:22Z" - latency: 2.223607ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:23:22Z" - latency: 956.246µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:22Z" - latency: 2.049087ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:22:22Z" - latency: 916.429µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:22Z" - latency: 2.469064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:21:22Z" - latency: 1.350051ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:22Z" - latency: 1.945573ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:20:22Z" kind: List metadata: resourceVersion: ""