apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:17:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-11-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-11.ec2.internal uid: b614e2c3-7994-44d9-9d24-3be444471fc0 resourceVersion: "54545" uid: 1626faa4-a5b9-4729-bb47-7b4561a6ce84 spec: sourcePod: network-check-source-989f8b8dc-lb5l7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T15:24:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.204708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:52:41Z" - latency: 1.220231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:51:41Z" - latency: 973.758µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:50:41Z" - latency: 838.759µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:49:41Z" - latency: 1.115117ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:48:41Z" - latency: 902.142µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:47:41Z" - latency: 1.621074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:46:41Z" - latency: 1.305846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:45:41Z" - latency: 1.038403ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:44:41Z" - latency: 1.435109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:43:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:17:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-11-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-11.ec2.internal uid: b614e2c3-7994-44d9-9d24-3be444471fc0 resourceVersion: "55516" uid: d1400d42-dbe9-4a5f-94ba-ef78ef4cff6a spec: sourcePod: network-check-source-989f8b8dc-lb5l7 targetEndpoint: ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:23:41Z" message: 'load-balancer-api-external: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.249503ms message: 'load-balancer-api-external: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:53:41Z" - latency: 10.740589ms message: 'load-balancer-api-external: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:53:41Z" - latency: 7.470234ms message: 'load-balancer-api-external: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:52:41Z" - latency: 9.941308ms message: 'load-balancer-api-external: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:52:41Z" - latency: 4.00098ms message: 'load-balancer-api-external: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:51:41Z" - latency: 10.412966ms message: 'load-balancer-api-external: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:51:41Z" - latency: 10.867718ms message: 'load-balancer-api-external: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:50:41Z" - latency: 8.680169ms message: 'load-balancer-api-external: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:50:41Z" - latency: 3.617008ms message: 'load-balancer-api-external: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:49:41Z" - latency: 7.533271ms message: 'load-balancer-api-external: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:49:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:17:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-11-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-11.ec2.internal uid: b614e2c3-7994-44d9-9d24-3be444471fc0 resourceVersion: "55515" uid: 9ef91214-bc92-47e2-87f2-f9e59e649cea spec: sourcePod: network-check-source-989f8b8dc-lb5l7 targetEndpoint: ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:23:41Z" message: 'load-balancer-api-internal: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.232102ms message: 'load-balancer-api-internal: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:53:41Z" - latency: 10.888475ms message: 'load-balancer-api-internal: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:53:41Z" - latency: 7.422308ms message: 'load-balancer-api-internal: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:52:41Z" - latency: 10.132774ms message: 'load-balancer-api-internal: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:52:41Z" - latency: 4.418554ms message: 'load-balancer-api-internal: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:51:41Z" - latency: 10.367505ms message: 'load-balancer-api-internal: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:51:41Z" - latency: 8.623654ms message: 'load-balancer-api-internal: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:50:41Z" - latency: 8.81723ms message: 'load-balancer-api-internal: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:50:41Z" - latency: 6.950344ms message: 'load-balancer-api-internal: tcp connection to ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:49:41Z" - latency: 7.676381ms message: 'load-balancer-api-internal: resolved host name ad45aa920f71847e6951010c55fd3dad-24c822e8c8c12690.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T15:49:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:17:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-11-to-network-check-target-ip-10-0-131-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-11.ec2.internal uid: b614e2c3-7994-44d9-9d24-3be444471fc0 resourceVersion: "54544" uid: f20a9ecc-5791-4ce7-97c3-18d33cc3db5c spec: sourcePod: network-check-source-989f8b8dc-lb5l7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:24:41Z" message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.978064ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:52:41Z" - latency: 1.883396ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:51:41Z" - latency: 2.085075ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:50:41Z" - latency: 1.803171ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:49:41Z" - latency: 1.97647ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:48:41Z" - latency: 1.590925ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:47:41Z" - latency: 1.997282ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:46:41Z" - latency: 1.989763ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:45:41Z" - latency: 1.982124ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:44:41Z" - latency: 1.935461ms message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:43:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:17:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-11-to-network-check-target-ip-10-0-138-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-11.ec2.internal uid: b614e2c3-7994-44d9-9d24-3be444471fc0 resourceVersion: "54542" uid: fcf5b804-61c6-4190-94cd-e957691fea40 spec: sourcePod: network-check-source-989f8b8dc-lb5l7 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:24:41Z" message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.145712ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:52:41Z" - latency: 962.119µs message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:51:41Z" - latency: 876.076µs message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:50:41Z" - latency: 789.347µs message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:49:41Z" - latency: 1.619604ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:48:41Z" - latency: 810.802µs message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:47:41Z" - latency: 1.296501ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:46:41Z" - latency: 941.303µs message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:45:41Z" - latency: 915.218µs message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:44:41Z" - latency: 1.19133ms message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:43:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:17:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-11-to-network-check-target-ip-10-0-140-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-11.ec2.internal uid: b614e2c3-7994-44d9-9d24-3be444471fc0 resourceVersion: "54543" uid: 6512905d-c3ab-489b-a8f3-3ca301ff7e1c spec: sourcePod: network-check-source-989f8b8dc-lb5l7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:24:41Z" message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.044071ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:52:41Z" - latency: 1.953804ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:51:41Z" - latency: 1.717617ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:50:41Z" - latency: 2.007555ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:49:41Z" - latency: 2.453879ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:48:41Z" - latency: 1.828424ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:47:41Z" - latency: 2.147291ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:46:41Z" - latency: 2.000814ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:45:41Z" - latency: 2.153557ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:44:41Z" - latency: 2.133473ms message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:43:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:17:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-11-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-11.ec2.internal uid: b614e2c3-7994-44d9-9d24-3be444471fc0 resourceVersion: "55513" uid: 46111a4b-971d-4fb2-937c-cff68d5b3fcc spec: sourcePod: network-check-source-989f8b8dc-lb5l7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T15:23:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.41µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:53:41Z" - latency: 1.631226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:53:41Z" - latency: 897.419µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:52:41Z" - latency: 2.948872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:52:41Z" - latency: 923.95µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:51:41Z" - latency: 1.665498ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:51:41Z" - latency: 835.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:50:41Z" - latency: 1.819003ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:50:41Z" - latency: 817.986µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T15:49:41Z" - latency: 1.628933ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T15:49:41Z" kind: List metadata: resourceVersion: ""