apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 4620d810-321d-4811-9e5b-e0c90015210b resourceVersion: "37670" uid: 025144ce-dcea-48c7-b0a9-46544bed3f6a spec: sourcePod: network-check-source-7bc5b6bf85-jms4h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T18:27:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.754µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:41:05Z" - latency: 1.131896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:40:05Z" - latency: 1.233082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:39:05Z" - latency: 1.120708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:38:05Z" - latency: 1.1277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:37:05Z" - latency: 1.445361ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:36:05Z" - latency: 1.05558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:35:05Z" - latency: 965.222µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:34:05Z" - latency: 870.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:33:05Z" - latency: 1.086863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:32:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 4620d810-321d-4811-9e5b-e0c90015210b resourceVersion: "41336" uid: 4539756c-5027-4704-ab82-9b135d48cdbf spec: sourcePod: network-check-source-7bc5b6bf85-jms4h targetEndpoint: abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:26:05Z" message: 'load-balancer-api-external: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.918387ms message: 'load-balancer-api-external: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:44:05Z" - latency: 6.930009ms message: 'load-balancer-api-external: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:44:05Z" - latency: 4.148766ms message: 'load-balancer-api-external: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:43:05Z" - latency: 6.59525ms message: 'load-balancer-api-external: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:43:05Z" - latency: 5.88559ms message: 'load-balancer-api-external: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:42:05Z" - latency: 6.544056ms message: 'load-balancer-api-external: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:42:05Z" - latency: 5.768014ms message: 'load-balancer-api-external: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:41:05Z" - latency: 7.266856ms message: 'load-balancer-api-external: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:41:05Z" - latency: 5.134214ms message: 'load-balancer-api-external: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:40:05Z" - latency: 6.416151ms message: 'load-balancer-api-external: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:40:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 4620d810-321d-4811-9e5b-e0c90015210b resourceVersion: "41337" uid: 39dc69c4-a1de-4ef2-86e7-e559d112825d spec: sourcePod: network-check-source-7bc5b6bf85-jms4h targetEndpoint: abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T18:26:05Z" message: 'load-balancer-api-internal: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.933393ms message: 'load-balancer-api-internal: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:44:05Z" - latency: 6.940638ms message: 'load-balancer-api-internal: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:44:05Z" - latency: 4.149953ms message: 'load-balancer-api-internal: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:43:05Z" - latency: 6.63358ms message: 'load-balancer-api-internal: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:43:05Z" - latency: 4.431611ms message: 'load-balancer-api-internal: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:42:05Z" - latency: 6.569032ms message: 'load-balancer-api-internal: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:42:05Z" - latency: 5.357683ms message: 'load-balancer-api-internal: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:41:05Z" - latency: 7.356668ms message: 'load-balancer-api-internal: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:41:05Z" - latency: 5.132342ms message: 'load-balancer-api-internal: tcp connection to abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:40:05Z" - latency: 6.326716ms message: 'load-balancer-api-internal: resolved host name abf2d44353a5c4ffbbeaa63543a6769a-68a638e374c7ed45.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T18:40:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-136-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 4620d810-321d-4811-9e5b-e0c90015210b resourceVersion: "37668" uid: fa28e1d5-9954-4c8f-b0e4-57b53febf292 spec: sourcePod: network-check-source-7bc5b6bf85-jms4h targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:27:05Z" message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.495882ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:41:05Z" - latency: 2.392127ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:40:05Z" - latency: 2.493549ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:39:05Z" - latency: 2.287657ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:38:05Z" - latency: 2.464193ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:37:05Z" - latency: 2.651125ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:36:05Z" - latency: 2.657722ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:35:05Z" - latency: 2.280417ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:34:05Z" - latency: 2.288753ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:33:05Z" - latency: 2.316197ms message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:32:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-138-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 4620d810-321d-4811-9e5b-e0c90015210b resourceVersion: "37669" uid: 0f748829-0ebf-4dc4-89d0-a4b5575bdffd spec: sourcePod: network-check-source-7bc5b6bf85-jms4h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:27:05Z" message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.096648ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:41:05Z" - latency: 2.517531ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:40:05Z" - latency: 2.544946ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:39:05Z" - latency: 2.272466ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:38:05Z" - latency: 2.854825ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:37:05Z" - latency: 2.158847ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:36:05Z" - latency: 2.323929ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:35:05Z" - latency: 2.225838ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:34:05Z" - latency: 2.647885ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:33:05Z" - latency: 2.395729ms message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:32:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-ip-10-0-141-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 4620d810-321d-4811-9e5b-e0c90015210b resourceVersion: "37667" uid: 57a15c54-683a-43a1-b802-fd27f8251187 spec: sourcePod: network-check-source-7bc5b6bf85-jms4h targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T18:27:05Z" message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.693µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:41:05Z" - latency: 983.988µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:40:05Z" - latency: 1.39255ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:39:05Z" - latency: 925.301µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:38:05Z" - latency: 956.311µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:37:05Z" - latency: 962.986µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:36:05Z" - latency: 874.505µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:35:05Z" - latency: 941.735µs message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:34:05Z" - latency: 1.520197ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:33:05Z" - latency: 1.00869ms message: 'network-check-target-ip-10-0-141-186: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:32:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T18:20:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-186-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-186.ec2.internal uid: 4620d810-321d-4811-9e5b-e0c90015210b resourceVersion: "41334" uid: c9ce831d-46a8-4404-9d1e-5e9bbf5ea652 spec: sourcePod: network-check-source-7bc5b6bf85-jms4h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T18:26:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.130754ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:44:05Z" - latency: 1.834386ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:44:05Z" - latency: 1.074997ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:43:05Z" - latency: 1.658521ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:43:05Z" - latency: 1.076363ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:42:05Z" - latency: 2.001647ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:42:05Z" - latency: 887.895µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:41:05Z" - latency: 1.911004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:41:05Z" - latency: 1.160436ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T18:40:05Z" - latency: 1.750969ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T18:40:05Z" kind: List metadata: resourceVersion: ""