apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T13:38:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 6cffcf9e-2b40-4ec0-b75c-4fd2ddc77031 resourceVersion: "57682" uid: f63605df-740e-4901-b4d5-f3c536652cf3 spec: sourcePod: network-check-source-7bc5b6bf85-kr49n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-18T13:45:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.252532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:13:52Z" - latency: 1.102843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:12:52Z" - latency: 774µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:11:52Z" - latency: 857.813µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:10:52Z" - latency: 725.149µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:09:52Z" - latency: 930.858µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:08:52Z" - latency: 785.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:07:52Z" - latency: 774.152µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:06:52Z" - latency: 1.006833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:05:52Z" - latency: 1.069068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:04:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T13:38:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 6cffcf9e-2b40-4ec0-b75c-4fd2ddc77031 resourceVersion: "58522" uid: 3c49f3d6-c5c8-43a2-b498-8db0be7cc57b spec: sourcePod: network-check-source-7bc5b6bf85-kr49n targetEndpoint: a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T13:44:52Z" message: 'load-balancer-api-external: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.116767ms message: 'load-balancer-api-external: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:14:52Z" - latency: 6.899532ms message: 'load-balancer-api-external: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:14:52Z" - latency: 4.161058ms message: 'load-balancer-api-external: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:13:52Z" - latency: 6.193373ms message: 'load-balancer-api-external: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:13:52Z" - latency: 5.28726ms message: 'load-balancer-api-external: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:12:52Z" - latency: 8.408512ms message: 'load-balancer-api-external: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:12:52Z" - latency: 4.900467ms message: 'load-balancer-api-external: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:11:52Z" - latency: 8.708842ms message: 'load-balancer-api-external: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:11:52Z" - latency: 4.740047ms message: 'load-balancer-api-external: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:10:52Z" - latency: 7.376087ms message: 'load-balancer-api-external: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:10:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T13:38:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 6cffcf9e-2b40-4ec0-b75c-4fd2ddc77031 resourceVersion: "58523" uid: 4a413fe6-93be-4bb6-9edd-b784e8483fab spec: sourcePod: network-check-source-7bc5b6bf85-kr49n targetEndpoint: a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T13:44:52Z" message: 'load-balancer-api-internal: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.157876ms message: 'load-balancer-api-internal: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:14:52Z" - latency: 6.820649ms message: 'load-balancer-api-internal: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:14:52Z" - latency: 4.971311ms message: 'load-balancer-api-internal: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:13:52Z" - latency: 6.158819ms message: 'load-balancer-api-internal: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:13:52Z" - latency: 5.341665ms message: 'load-balancer-api-internal: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:12:52Z" - latency: 8.352572ms message: 'load-balancer-api-internal: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:12:52Z" - latency: 5.120149ms message: 'load-balancer-api-internal: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:11:52Z" - latency: 8.604705ms message: 'load-balancer-api-internal: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:11:52Z" - latency: 4.715079ms message: 'load-balancer-api-internal: tcp connection to a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:10:52Z" - latency: 7.420971ms message: 'load-balancer-api-internal: resolved host name a228a5296217f4410b81918884b9d7d2-d4afe4d93c3bb4b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T14:10:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T13:38:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-128-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 6cffcf9e-2b40-4ec0-b75c-4fd2ddc77031 resourceVersion: "57679" uid: cd7cab53-0d66-4a44-81a1-bee327855d9f spec: sourcePod: network-check-source-7bc5b6bf85-kr49n targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-18T13:45:52Z" message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.158538ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:13:52Z" - latency: 1.52676ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:12:52Z" - latency: 1.080331ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:11:52Z" - latency: 1.017502ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:10:52Z" - latency: 1.468273ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:09:52Z" - latency: 784.189µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:08:52Z" - latency: 1.122743ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:07:52Z" - latency: 779.561µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:06:52Z" - latency: 839.97µs message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:05:52Z" - latency: 1.129777ms message: 'network-check-target-ip-10-0-128-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:04:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T13:38:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-135-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 6cffcf9e-2b40-4ec0-b75c-4fd2ddc77031 resourceVersion: "57680" uid: b4f99473-578e-4769-b4b5-529c46989004 spec: sourcePod: network-check-source-7bc5b6bf85-kr49n targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-18T13:45:52Z" message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.70744ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:13:52Z" - latency: 2.295774ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:12:52Z" - latency: 1.561403ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:11:52Z" - latency: 1.803819ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:10:52Z" - latency: 1.601905ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:09:52Z" - latency: 1.78821ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:08:52Z" - latency: 2.158028ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:07:52Z" - latency: 1.722338ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:06:52Z" - latency: 1.865585ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:05:52Z" - latency: 1.599373ms message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:04:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T13:38:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-ip-10-0-136-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 6cffcf9e-2b40-4ec0-b75c-4fd2ddc77031 resourceVersion: "57681" uid: 742e3d71-83a9-49b7-944a-5053923c5be4 spec: sourcePod: network-check-source-7bc5b6bf85-kr49n targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-18T13:45:52Z" message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.270776ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:13:52Z" - latency: 2.30094ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:12:52Z" - latency: 2.363615ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:11:52Z" - latency: 2.104241ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:10:52Z" - latency: 2.449927ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:09:52Z" - latency: 2.083674ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:08:52Z" - latency: 2.578046ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:07:52Z" - latency: 2.544582ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:06:52Z" - latency: 2.305478ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:05:52Z" - latency: 1.963209ms message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:04:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T13:38:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-123-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-123.ec2.internal uid: 6cffcf9e-2b40-4ec0-b75c-4fd2ddc77031 resourceVersion: "58521" uid: bb4f5303-0d48-4bdd-a1c6-6070972336e7 spec: sourcePod: network-check-source-7bc5b6bf85-kr49n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-18T13:44:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.124048ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:14:52Z" - latency: 2.231549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T14:14:52Z" - latency: 1.129236ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:13:52Z" - latency: 1.921393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T14:13:52Z" - latency: 1.013311ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:12:52Z" - latency: 1.823344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T14:12:52Z" - latency: 1.22635ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:11:52Z" - latency: 1.787026ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T14:11:52Z" - latency: 954.021µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T14:10:52Z" - latency: 1.780936ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T14:10:52Z" kind: List metadata: resourceVersion: ""