apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-40-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-40.ec2.internal uid: e7d92848-d305-4bca-9aa0-41c19011f167 resourceVersion: "57753" uid: 210d134c-09cf-4ab9-93f3-07e8b95a9cb0 spec: sourcePod: network-check-source-6f78d59f99-8bw88 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T16:28:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.124678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:49:24Z" - latency: 1.982093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:48:24Z" - latency: 1.735028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:47:24Z" - latency: 918.253µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:46:24Z" - latency: 1.222448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:45:24Z" - latency: 1.284822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:44:24Z" - latency: 1.365704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:43:24Z" - latency: 1.476165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:42:24Z" - latency: 1.288551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:41:24Z" - latency: 1.315455ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:40:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-40-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-40.ec2.internal uid: e7d92848-d305-4bca-9aa0-41c19011f167 resourceVersion: "59977" uid: 452967c4-15c2-4fe7-8f75-4204c25120b0 spec: sourcePod: network-check-source-6f78d59f99-8bw88 targetEndpoint: a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T16:27:24Z" message: 'load-balancer-api-external: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 34.397836ms message: 'load-balancer-api-external: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:51:24Z" - latency: 7.833089ms message: 'load-balancer-api-external: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:51:24Z" - latency: 16.869395ms message: 'load-balancer-api-external: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:50:24Z" - latency: 6.556333ms message: 'load-balancer-api-external: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:50:24Z" - latency: 15.095126ms message: 'load-balancer-api-external: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:49:24Z" - latency: 8.80327ms message: 'load-balancer-api-external: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:49:24Z" - latency: 17.074305ms message: 'load-balancer-api-external: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:48:24Z" - latency: 10.783311ms message: 'load-balancer-api-external: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:48:24Z" - latency: 17.633658ms message: 'load-balancer-api-external: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:47:24Z" - latency: 7.256351ms message: 'load-balancer-api-external: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-40-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-40.ec2.internal uid: e7d92848-d305-4bca-9aa0-41c19011f167 resourceVersion: "59976" uid: ec3e63f1-7395-426f-9ef6-778d8e139b89 spec: sourcePod: network-check-source-6f78d59f99-8bw88 targetEndpoint: a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T16:27:24Z" message: 'load-balancer-api-internal: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 25.082608ms message: 'load-balancer-api-internal: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:51:24Z" - latency: 7.75611ms message: 'load-balancer-api-internal: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:51:24Z" - latency: 16.135265ms message: 'load-balancer-api-internal: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:50:24Z" - latency: 6.540914ms message: 'load-balancer-api-internal: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:50:24Z" - latency: 14.737912ms message: 'load-balancer-api-internal: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:49:24Z" - latency: 8.77253ms message: 'load-balancer-api-internal: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:49:24Z" - latency: 15.958168ms message: 'load-balancer-api-internal: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:48:24Z" - latency: 10.79408ms message: 'load-balancer-api-internal: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:48:24Z" - latency: 21.968567ms message: 'load-balancer-api-internal: tcp connection to a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:47:24Z" - latency: 7.203727ms message: 'load-balancer-api-internal: resolved host name a7cbd2cdce92743e7b7fe9b9294a8eb9-2b7d31d50100387a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T16:47:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-40-to-network-check-target-ip-10-0-137-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-40.ec2.internal uid: e7d92848-d305-4bca-9aa0-41c19011f167 resourceVersion: "57752" uid: 0874d22d-93aa-45d6-ba40-fd16c38c5aa0 spec: sourcePod: network-check-source-6f78d59f99-8bw88 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T16:28:24Z" message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.006361ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:49:24Z" - latency: 3.337548ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:48:24Z" - latency: 2.357319ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:47:24Z" - latency: 2.353076ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:46:24Z" - latency: 2.248791ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:45:24Z" - latency: 2.36192ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:44:24Z" - latency: 2.414416ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:43:24Z" - latency: 2.421274ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:42:24Z" - latency: 2.452429ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:41:24Z" - latency: 2.233557ms message: 'network-check-target-ip-10-0-137-219: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:40:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-40-to-network-check-target-ip-10-0-138-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-40.ec2.internal uid: e7d92848-d305-4bca-9aa0-41c19011f167 resourceVersion: "57750" uid: 57083aa4-6557-415c-b77f-642e12fc6aac spec: sourcePod: network-check-source-6f78d59f99-8bw88 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T16:28:24Z" message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.829083ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:49:24Z" - latency: 2.649993ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:48:24Z" - latency: 2.11069ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:47:24Z" - latency: 1.705256ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:46:24Z" - latency: 2.04386ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:45:24Z" - latency: 2.155951ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:44:24Z" - latency: 1.998827ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:43:24Z" - latency: 2.334319ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:42:24Z" - latency: 2.107291ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:41:24Z" - latency: 1.483628ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:40:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-40-to-network-check-target-ip-10-0-138-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-40.ec2.internal uid: e7d92848-d305-4bca-9aa0-41c19011f167 resourceVersion: "57751" uid: f4f2beae-4349-4604-b0ea-7c26c1dc89db spec: sourcePod: network-check-source-6f78d59f99-8bw88 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T16:28:24Z" message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.05192ms message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:49:24Z" - latency: 1.126439ms message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:48:24Z" - latency: 1.027128ms message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:47:24Z" - latency: 1.568633ms message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:46:24Z" - latency: 996.663µs message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:45:24Z" - latency: 980.852µs message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:44:24Z" - latency: 974.427µs message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:43:24Z" - latency: 1.292282ms message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:42:24Z" - latency: 907.317µs message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:41:24Z" - latency: 1.751541ms message: 'network-check-target-ip-10-0-138-40: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:40:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:21:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-40-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-40.ec2.internal uid: e7d92848-d305-4bca-9aa0-41c19011f167 resourceVersion: "59975" uid: 32602398-12c2-4929-b63a-52bb1d38f66c spec: sourcePod: network-check-source-6f78d59f99-8bw88 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T16:27:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.689µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:51:24Z" - latency: 1.749024ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:51:24Z" - latency: 843.614µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:50:24Z" - latency: 1.825539ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:50:24Z" - latency: 838.801µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:49:24Z" - latency: 2.176574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:49:24Z" - latency: 1.09101ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:48:24Z" - latency: 2.589674ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:48:24Z" - latency: 854.181µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T16:47:24Z" - latency: 1.664523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T16:47:24Z" kind: List metadata: resourceVersion: ""