apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T18:00:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-122-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-122.ec2.internal uid: 75e72687-fec1-4b5c-9b74-d29adafe049f resourceVersion: "19493" uid: b55fd164-4247-410f-bb33-b5edd456abff spec: sourcePod: network-check-source-56d84b9f44-rp8nn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T18:07:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 933.249µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:21:44Z" - latency: 1.048823ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:20:44Z" - latency: 856.501µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:19:44Z" - latency: 893.398µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:18:44Z" - latency: 869.01µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:17:44Z" - latency: 841.74µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:16:44Z" - latency: 825.616µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:15:44Z" - latency: 778.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:14:44Z" - latency: 1.246039ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:13:44Z" - latency: 860.728µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:12:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T18:00:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-122-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-122.ec2.internal uid: 75e72687-fec1-4b5c-9b74-d29adafe049f resourceVersion: "20651" uid: 353ac5dd-9d4c-463a-becf-1de9864312f8 spec: sourcePod: network-check-source-56d84b9f44-rp8nn targetEndpoint: a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T18:06:44Z" message: 'load-balancer-api-external: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.081445ms message: 'load-balancer-api-external: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:24:44Z" - latency: 8.463475ms message: 'load-balancer-api-external: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:24:44Z" - latency: 5.277326ms message: 'load-balancer-api-external: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:23:44Z" - latency: 7.808744ms message: 'load-balancer-api-external: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:23:44Z" - latency: 7.570128ms message: 'load-balancer-api-external: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:22:44Z" - latency: 7.933195ms message: 'load-balancer-api-external: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:22:44Z" - latency: 5.414946ms message: 'load-balancer-api-external: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:21:44Z" - latency: 7.942585ms message: 'load-balancer-api-external: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:21:44Z" - latency: 4.142248ms message: 'load-balancer-api-external: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:20:44Z" - latency: 8.281699ms message: 'load-balancer-api-external: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:20:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T18:00:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-122-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-122.ec2.internal uid: 75e72687-fec1-4b5c-9b74-d29adafe049f resourceVersion: "20652" uid: dc73082a-a630-4f40-a515-096e5807015d spec: sourcePod: network-check-source-56d84b9f44-rp8nn targetEndpoint: a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T18:06:44Z" message: 'load-balancer-api-internal: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.076715ms message: 'load-balancer-api-internal: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:24:44Z" - latency: 8.412061ms message: 'load-balancer-api-internal: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:24:44Z" - latency: 4.251086ms message: 'load-balancer-api-internal: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:23:44Z" - latency: 7.787034ms message: 'load-balancer-api-internal: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:23:44Z" - latency: 7.494305ms message: 'load-balancer-api-internal: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:22:44Z" - latency: 7.86034ms message: 'load-balancer-api-internal: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:22:44Z" - latency: 5.392915ms message: 'load-balancer-api-internal: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:21:44Z" - latency: 7.896031ms message: 'load-balancer-api-internal: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:21:44Z" - latency: 4.084545ms message: 'load-balancer-api-internal: tcp connection to a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:20:44Z" - latency: 8.258687ms message: 'load-balancer-api-internal: resolved host name a811ab16225194c95a15f261453bbff1-e8954ca262516eca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:20:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T18:00:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-122-to-network-check-target-ip-10-0-128-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-122.ec2.internal uid: 75e72687-fec1-4b5c-9b74-d29adafe049f resourceVersion: "19490" uid: 08825135-b4e1-460e-a355-03ec970542dc spec: sourcePod: network-check-source-56d84b9f44-rp8nn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T18:07:44Z" message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 853.956µs message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:21:44Z" - latency: 917.993µs message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:20:44Z" - latency: 791.7µs message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:19:44Z" - latency: 831.423µs message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:18:44Z" - latency: 1.110164ms message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:17:44Z" - latency: 1.148542ms message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:16:44Z" - latency: 811.202µs message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:15:44Z" - latency: 762.23µs message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:14:44Z" - latency: 799.136µs message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:13:44Z" - latency: 1.31224ms message: 'network-check-target-ip-10-0-128-122: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:12:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T18:00:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-122-to-network-check-target-ip-10-0-133-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-122.ec2.internal uid: 75e72687-fec1-4b5c-9b74-d29adafe049f resourceVersion: "19492" uid: 06c7b0b2-72f5-4228-a740-71b71d82c0af spec: sourcePod: network-check-source-56d84b9f44-rp8nn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T18:07:44Z" message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.091782ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:21:44Z" - latency: 2.247964ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:20:44Z" - latency: 2.011672ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:19:44Z" - latency: 2.041341ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:18:44Z" - latency: 2.006409ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:17:44Z" - latency: 2.17975ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:16:44Z" - latency: 2.630157ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:15:44Z" - latency: 1.94467ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:14:44Z" - latency: 1.980374ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:13:44Z" - latency: 2.253543ms message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:12:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T18:00:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-122-to-network-check-target-ip-10-0-143-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-122.ec2.internal uid: 75e72687-fec1-4b5c-9b74-d29adafe049f resourceVersion: "19491" uid: 20e065b2-dcce-4fed-b6f3-05d77e33bd77 spec: sourcePod: network-check-source-56d84b9f44-rp8nn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-29T18:07:44Z" message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.094163ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:21:44Z" - latency: 1.914656ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:20:44Z" - latency: 2.023722ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:19:44Z" - latency: 1.568038ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:18:44Z" - latency: 1.882228ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:17:44Z" - latency: 1.966163ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:16:44Z" - latency: 2.21699ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:15:44Z" - latency: 2.148049ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:14:44Z" - latency: 8.23486ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:13:44Z" - latency: 1.957296ms message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:12:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T18:00:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-122-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-122.ec2.internal uid: 75e72687-fec1-4b5c-9b74-d29adafe049f resourceVersion: "20650" uid: 70d07a7a-0859-479d-bc22-52284e9d3466 spec: sourcePod: network-check-source-56d84b9f44-rp8nn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T18:06:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 788.439µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:24:44Z" - latency: 1.654385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T18:24:44Z" - latency: 925.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:23:44Z" - latency: 2.105363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T18:23:44Z" - latency: 765.125µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:22:44Z" - latency: 1.56506ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T18:22:44Z" - latency: 792.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:21:44Z" - latency: 1.842933ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T18:21:44Z" - latency: 779.609µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:20:44Z" - latency: 1.80269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T18:20:44Z" kind: List metadata: resourceVersion: ""