apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:20:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.us-east-2.compute.internal uid: 75332fb7-aac0-4e67-b999-d59f5023c6ef resourceVersion: "71944" uid: 0b66f7a7-8b08-4087-be52-1b4e17494305 spec: sourcePod: network-check-source-6f78d59f99-5s5g6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T22:27:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.480344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:37:01Z" - latency: 1.327851ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:36:01Z" - latency: 1.302184ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:35:01Z" - latency: 1.039969ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:34:01Z" - latency: 1.027785ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:33:01Z" - latency: 1.27388ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:32:01Z" - latency: 1.179201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:31:01Z" - latency: 1.297212ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:30:01Z" - latency: 1.605802ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:29:01Z" - latency: 1.102919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:28:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:20:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.us-east-2.compute.internal uid: 75332fb7-aac0-4e67-b999-d59f5023c6ef resourceVersion: "72272" uid: 2afb10f9-16db-47d3-8e38-20ad8cd9b6a4 spec: sourcePod: network-check-source-6f78d59f99-5s5g6 targetEndpoint: ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:26:01Z" message: 'load-balancer-api-external: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.84995ms message: 'load-balancer-api-external: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:38:01Z" - latency: 6.585985ms message: 'load-balancer-api-external: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:38:01Z" - latency: 5.836513ms message: 'load-balancer-api-external: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:37:01Z" - latency: 8.225755ms message: 'load-balancer-api-external: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:37:01Z" - latency: 6.152695ms message: 'load-balancer-api-external: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:36:01Z" - latency: 6.655042ms message: 'load-balancer-api-external: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:36:01Z" - latency: 5.432592ms message: 'load-balancer-api-external: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:35:01Z" - latency: 7.231971ms message: 'load-balancer-api-external: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:35:01Z" - latency: 6.453589ms message: 'load-balancer-api-external: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:34:01Z" - latency: 6.397006ms message: 'load-balancer-api-external: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:34:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:20:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.us-east-2.compute.internal uid: 75332fb7-aac0-4e67-b999-d59f5023c6ef resourceVersion: "72271" uid: 9738dcff-cc2b-4ece-a324-7ba3072c73ad spec: sourcePod: network-check-source-6f78d59f99-5s5g6 targetEndpoint: ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:26:01Z" message: 'load-balancer-api-internal: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.878462ms message: 'load-balancer-api-internal: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:38:01Z" - latency: 6.695073ms message: 'load-balancer-api-internal: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:38:01Z" - latency: 5.762981ms message: 'load-balancer-api-internal: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:37:01Z" - latency: 8.264784ms message: 'load-balancer-api-internal: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:37:01Z" - latency: 6.184623ms message: 'load-balancer-api-internal: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:36:01Z" - latency: 6.599784ms message: 'load-balancer-api-internal: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:36:01Z" - latency: 5.439547ms message: 'load-balancer-api-internal: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:35:01Z" - latency: 7.204571ms message: 'load-balancer-api-internal: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:35:01Z" - latency: 6.445677ms message: 'load-balancer-api-internal: tcp connection to ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:34:01Z" - latency: 6.474777ms message: 'load-balancer-api-internal: resolved host name ae09c812c6e404d9a80b724db9fbfb35-422a5c72c4122098.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:34:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:20:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-network-check-target-ip-10-0-128-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.us-east-2.compute.internal uid: 75332fb7-aac0-4e67-b999-d59f5023c6ef resourceVersion: "71692" uid: bb359942-14d0-48f2-a3fc-d8338e0d1730 spec: sourcePod: network-check-source-6f78d59f99-5s5g6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:27:01Z" message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.161271ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:37:01Z" - latency: 1.985025ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:36:01Z" - latency: 1.945268ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:35:01Z" - latency: 2.469646ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:34:01Z" - latency: 2.395775ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:33:01Z" - latency: 1.910871ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:32:01Z" - latency: 2.369539ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:31:01Z" - latency: 2.112511ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:30:01Z" - latency: 2.025358ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:29:01Z" - latency: 2.148791ms message: 'network-check-target-ip-10-0-128-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:28:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:20:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-network-check-target-ip-10-0-132-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.us-east-2.compute.internal uid: 75332fb7-aac0-4e67-b999-d59f5023c6ef resourceVersion: "71691" uid: 198862e9-9bb6-4d27-85dd-5baecc92aa72 spec: sourcePod: network-check-source-6f78d59f99-5s5g6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:27:01Z" message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.915076ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:37:01Z" - latency: 2.638566ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:36:01Z" - latency: 2.466006ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:35:01Z" - latency: 2.280624ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:34:01Z" - latency: 2.389303ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:33:01Z" - latency: 2.299567ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:32:01Z" - latency: 2.435276ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:31:01Z" - latency: 2.607787ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:30:01Z" - latency: 3.028779ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:29:01Z" - latency: 2.445957ms message: 'network-check-target-ip-10-0-132-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:28:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:20:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-network-check-target-ip-10-0-138-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.us-east-2.compute.internal uid: 75332fb7-aac0-4e67-b999-d59f5023c6ef resourceVersion: "71690" uid: 97f293be-3e92-4cbd-b16f-85ddd09b1af8 spec: sourcePod: network-check-source-6f78d59f99-5s5g6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:27:01Z" message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.820668ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:37:01Z" - latency: 1.466818ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:36:01Z" - latency: 1.399534ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:35:01Z" - latency: 1.070424ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:34:01Z" - latency: 937.225µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:33:01Z" - latency: 1.005698ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:32:01Z" - latency: 1.031578ms message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:31:01Z" - latency: 957.7µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:30:01Z" - latency: 989.038µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:29:01Z" - latency: 916.922µs message: 'network-check-target-ip-10-0-138-251: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:28:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T22:20:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-251-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-251.us-east-2.compute.internal uid: 75332fb7-aac0-4e67-b999-d59f5023c6ef resourceVersion: "72270" uid: a1446be8-475b-4496-9d5e-8902adcd1b01 spec: sourcePod: network-check-source-6f78d59f99-5s5g6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T22:26:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.705µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:38:01Z" - latency: 1.863403ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:38:01Z" - latency: 2.276988ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:37:01Z" - latency: 1.880095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:37:01Z" - latency: 1.047434ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:36:01Z" - latency: 1.639629ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:36:01Z" - latency: 936.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:35:01Z" - latency: 1.871946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:35:01Z" - latency: 1.383815ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:34:01Z" - latency: 1.871274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:34:01Z" kind: List metadata: resourceVersion: ""