apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:02:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-237-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-237.ec2.internal uid: c2cf3965-86c7-4c8c-832b-2a55b1a75935 resourceVersion: "57562" uid: 88ed76d9-e302-4505-8b14-ce3ff0b4e1eb spec: sourcePod: network-check-source-989f8b8dc-5t7tr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T19:09:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.274942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:51:03Z" - latency: 836.766µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:03Z" - latency: 926.737µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:03Z" - latency: 862.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:03Z" - latency: 1.161643ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:03Z" - latency: 1.117726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:03Z" - latency: 872.974µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:03Z" - latency: 1.033712ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:44:03Z" - latency: 880.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:43:03Z" - latency: 826.29µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:42:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:02:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-237-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-237.ec2.internal uid: c2cf3965-86c7-4c8c-832b-2a55b1a75935 resourceVersion: "56701" uid: 6a1efde4-0fb2-4f27-8742-3df1bf1ed6a3 spec: sourcePod: network-check-source-989f8b8dc-5t7tr targetEndpoint: aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T19:08:03Z" message: 'load-balancer-api-external: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.748894ms message: 'load-balancer-api-external: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:03Z" - latency: 6.648247ms message: 'load-balancer-api-external: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:50:03Z" - latency: 7.315341ms message: 'load-balancer-api-external: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:03Z" - latency: 6.706748ms message: 'load-balancer-api-external: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:49:03Z" - latency: 4.413642ms message: 'load-balancer-api-external: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:03Z" - latency: 11.696461ms message: 'load-balancer-api-external: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:48:03Z" - latency: 5.466733ms message: 'load-balancer-api-external: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:03Z" - latency: 6.939782ms message: 'load-balancer-api-external: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:47:03Z" - latency: 3.837678ms message: 'load-balancer-api-external: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:03Z" - latency: 10.290536ms message: 'load-balancer-api-external: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:46:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:02:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-237-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-237.ec2.internal uid: c2cf3965-86c7-4c8c-832b-2a55b1a75935 resourceVersion: "56702" uid: 702c398f-3e58-466b-bee4-4451c7102c1c spec: sourcePod: network-check-source-989f8b8dc-5t7tr targetEndpoint: aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T19:08:03Z" message: 'load-balancer-api-internal: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.243476ms message: 'load-balancer-api-internal: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:03Z" - latency: 6.618647ms message: 'load-balancer-api-internal: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:50:03Z" - latency: 5.087791ms message: 'load-balancer-api-internal: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:03Z" - latency: 6.829419ms message: 'load-balancer-api-internal: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:49:03Z" - latency: 5.800045ms message: 'load-balancer-api-internal: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:03Z" - latency: 11.675354ms message: 'load-balancer-api-internal: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:48:03Z" - latency: 6.788966ms message: 'load-balancer-api-internal: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:03Z" - latency: 6.862856ms message: 'load-balancer-api-internal: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:47:03Z" - latency: 5.799758ms message: 'load-balancer-api-internal: tcp connection to aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:03Z" - latency: 10.366558ms message: 'load-balancer-api-internal: resolved host name aa02cc370fcfb46c9bb69b2b56b189b2-b1b7f0f080e2fe4d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:46:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:02:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-237-to-network-check-target-ip-10-0-131-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-237.ec2.internal uid: c2cf3965-86c7-4c8c-832b-2a55b1a75935 resourceVersion: "57560" uid: 2d1be905-f4bf-400d-acb4-abde2398ce90 spec: sourcePod: network-check-source-989f8b8dc-5t7tr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:09:03Z" message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.222414ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:51:03Z" - latency: 1.932742ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:03Z" - latency: 1.817863ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:03Z" - latency: 3.319823ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:03Z" - latency: 1.90566ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:03Z" - latency: 2.284915ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:03Z" - latency: 2.07005ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:03Z" - latency: 2.037402ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:44:03Z" - latency: 2.275982ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:43:03Z" - latency: 2.061527ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:42:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:02:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-237-to-network-check-target-ip-10-0-141-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-237.ec2.internal uid: c2cf3965-86c7-4c8c-832b-2a55b1a75935 resourceVersion: "57559" uid: 55b2810a-559b-4478-9715-910cedd382a4 spec: sourcePod: network-check-source-989f8b8dc-5t7tr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:09:03Z" message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.45µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:51:03Z" - latency: 988.686µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:03Z" - latency: 784.8µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:03Z" - latency: 908.041µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:03Z" - latency: 868.239µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:03Z" - latency: 918.23µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:03Z" - latency: 885.73µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:03Z" - latency: 908.089µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:44:03Z" - latency: 1.008997ms message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:43:03Z" - latency: 807.431µs message: 'network-check-target-ip-10-0-141-237: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:42:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:02:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-237-to-network-check-target-ip-10-0-142-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-237.ec2.internal uid: c2cf3965-86c7-4c8c-832b-2a55b1a75935 resourceVersion: "57561" uid: d447d2da-b65d-43af-a09a-493199dcd67e spec: sourcePod: network-check-source-989f8b8dc-5t7tr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:09:03Z" message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.818443ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:51:03Z" - latency: 1.886736ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:03Z" - latency: 1.922675ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:03Z" - latency: 2.425731ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:03Z" - latency: 1.899441ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:03Z" - latency: 1.880016ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:03Z" - latency: 1.955351ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:45:03Z" - latency: 1.819796ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:44:03Z" - latency: 2.692132ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:43:03Z" - latency: 1.833084ms message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:42:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:02:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-237-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-237.ec2.internal uid: c2cf3965-86c7-4c8c-832b-2a55b1a75935 resourceVersion: "56700" uid: c44a6c14-de7c-4138-bf38-0937268d3ad5 spec: sourcePod: network-check-source-989f8b8dc-5t7tr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T19:08:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 832.203µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:03Z" - latency: 1.762696ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:50:03Z" - latency: 951.585µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:49:03Z" - latency: 1.75599ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:49:03Z" - latency: 954.032µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:48:03Z" - latency: 2.811909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:48:03Z" - latency: 1.068003ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:47:03Z" - latency: 1.603761ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:47:03Z" - latency: 803.812µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:46:03Z" - latency: 2.262381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:46:03Z" kind: List metadata: resourceVersion: ""