apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T23:16:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-139-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-139.ec2.internal uid: 433c581b-238c-4010-96e0-cc5c710b4a10 resourceVersion: "28642" uid: 226b6e71-18d0-41c3-aa54-2139a6f33ca5 spec: sourcePod: network-check-source-8894fc9bd-kj9pq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T23:23:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.09863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:30:31Z" - latency: 1.041936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:29:31Z" - latency: 889.674µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:28:31Z" - latency: 914.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:27:31Z" - latency: 1.038454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:26:31Z" - latency: 1.207812ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:25:31Z" - latency: 1.628799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:24:31Z" - latency: 989.145µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:23:31Z" - latency: 1.29894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:22:31Z" - latency: 811.429µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:21:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T23:16:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-139-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-139.ec2.internal uid: 433c581b-238c-4010-96e0-cc5c710b4a10 resourceVersion: "26334" uid: e21eb546-9254-4244-8990-a61695172145 spec: sourcePod: network-check-source-8894fc9bd-kj9pq targetEndpoint: a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T23:22:31Z" message: 'load-balancer-api-external: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.643346ms message: 'load-balancer-api-external: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:28:31Z" - latency: 7.826542ms message: 'load-balancer-api-external: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:28:31Z" - latency: 4.293007ms message: 'load-balancer-api-external: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:27:31Z" - latency: 8.240203ms message: 'load-balancer-api-external: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:27:31Z" - latency: 3.238167ms message: 'load-balancer-api-external: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:26:31Z" - latency: 11.102354ms message: 'load-balancer-api-external: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:26:31Z" - latency: 4.784877ms message: 'load-balancer-api-external: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:25:31Z" - latency: 7.810401ms message: 'load-balancer-api-external: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:25:31Z" - latency: 5.07704ms message: 'load-balancer-api-external: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:24:31Z" - latency: 10.210881ms message: 'load-balancer-api-external: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:24:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T23:16:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-139-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-139.ec2.internal uid: 433c581b-238c-4010-96e0-cc5c710b4a10 resourceVersion: "26333" uid: 047d016b-9ab4-4f70-85ed-9c797ffc52ae spec: sourcePod: network-check-source-8894fc9bd-kj9pq targetEndpoint: a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T23:22:31Z" message: 'load-balancer-api-internal: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.675257ms message: 'load-balancer-api-internal: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:28:31Z" - latency: 7.802118ms message: 'load-balancer-api-internal: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:28:31Z" - latency: 3.395441ms message: 'load-balancer-api-internal: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:27:31Z" - latency: 8.452025ms message: 'load-balancer-api-internal: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:27:31Z" - latency: 4.007472ms message: 'load-balancer-api-internal: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:26:31Z" - latency: 11.178984ms message: 'load-balancer-api-internal: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:26:31Z" - latency: 4.424915ms message: 'load-balancer-api-internal: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:25:31Z" - latency: 7.862855ms message: 'load-balancer-api-internal: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:25:31Z" - latency: 5.017061ms message: 'load-balancer-api-internal: tcp connection to a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:24:31Z" - latency: 10.287889ms message: 'load-balancer-api-internal: resolved host name a36480f41ca854e57b05f7ddbf4b1e5c-c1ea62063a97ea71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T23:24:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T23:16:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-139-to-network-check-target-ip-10-0-131-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-139.ec2.internal uid: 433c581b-238c-4010-96e0-cc5c710b4a10 resourceVersion: "28640" uid: af6c143d-21f2-4f9d-af86-19d0a3dba6d4 spec: sourcePod: network-check-source-8894fc9bd-kj9pq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T23:23:31Z" message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.763784ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:30:31Z" - latency: 1.922127ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:29:31Z" - latency: 1.795041ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:28:31Z" - latency: 1.599278ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:27:31Z" - latency: 1.492619ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:26:31Z" - latency: 1.645409ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:25:31Z" - latency: 1.948198ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:24:31Z" - latency: 1.739932ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:23:31Z" - latency: 1.761177ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:22:31Z" - latency: 1.605866ms message: 'network-check-target-ip-10-0-131-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:21:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T23:16:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-139-to-network-check-target-ip-10-0-134-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-139.ec2.internal uid: 433c581b-238c-4010-96e0-cc5c710b4a10 resourceVersion: "28641" uid: 02c7e885-1b6d-498a-a844-692e264fb308 spec: sourcePod: network-check-source-8894fc9bd-kj9pq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T23:23:31Z" message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.077044ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:30:31Z" - latency: 2.092522ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:29:31Z" - latency: 1.854775ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:28:31Z" - latency: 2.058263ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:27:31Z" - latency: 1.868138ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:26:31Z" - latency: 1.973069ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:25:31Z" - latency: 2.378133ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:24:31Z" - latency: 2.121951ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:23:31Z" - latency: 2.098957ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:22:31Z" - latency: 2.229503ms message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:21:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T23:16:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-139-to-network-check-target-ip-10-0-137-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-139.ec2.internal uid: 433c581b-238c-4010-96e0-cc5c710b4a10 resourceVersion: "28639" uid: 4e1bd0ee-3a0a-462e-979d-9710395ebdc7 spec: sourcePod: network-check-source-8894fc9bd-kj9pq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T23:23:31Z" message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.658µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:30:31Z" - latency: 819.329µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:29:31Z" - latency: 863.676µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:28:31Z" - latency: 749.284µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:27:31Z" - latency: 812.926µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:26:31Z" - latency: 821.101µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:25:31Z" - latency: 881.875µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:24:31Z" - latency: 748.312µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:23:31Z" - latency: 786.381µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:22:31Z" - latency: 881.4µs message: 'network-check-target-ip-10-0-137-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:21:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T23:16:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-139-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-139.ec2.internal uid: 433c581b-238c-4010-96e0-cc5c710b4a10 resourceVersion: "26332" uid: dde04f33-657d-485a-a29f-362d1ef0c9b7 spec: sourcePod: network-check-source-8894fc9bd-kj9pq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T23:22:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 748.55µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:28:31Z" - latency: 1.800824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T23:28:31Z" - latency: 811.612µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:27:31Z" - latency: 1.711311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T23:27:31Z" - latency: 822.22µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:26:31Z" - latency: 1.746407ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T23:26:31Z" - latency: 810.972µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:25:31Z" - latency: 1.721216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T23:25:31Z" - latency: 699.447µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T23:24:31Z" - latency: 2.701834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T23:24:31Z" kind: List metadata: resourceVersion: ""