apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:09:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-151-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-151.ec2.internal uid: 1ee57d4d-15ec-4a1c-8de1-22684548f4b9 resourceVersion: "31877" uid: 869f9a9a-6ead-4ed0-bc5f-13d6943a3ff3 spec: sourcePod: network-check-source-8894fc9bd-2dp7z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T19:16:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.011868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:51:54Z" - latency: 1.132726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:50:54Z" - latency: 1.033133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:49:54Z" - latency: 1.002697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:48:54Z" - latency: 970.366µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:47:54Z" - latency: 1.087701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:46:54Z" - latency: 1.066573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:45:54Z" - latency: 1.327324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:44:54Z" - latency: 1.055906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:43:54Z" - latency: 1.12845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:42:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:09:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-151-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-151.ec2.internal uid: 1ee57d4d-15ec-4a1c-8de1-22684548f4b9 resourceVersion: "31879" uid: 8479850c-253c-4b99-b994-bcfeeddd9a41 spec: sourcePod: network-check-source-8894fc9bd-2dp7z targetEndpoint: ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T19:15:54Z" message: 'load-balancer-api-external: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.944561ms message: 'load-balancer-api-external: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:51:54Z" - latency: 7.954528ms message: 'load-balancer-api-external: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:51:54Z" - latency: 4.383694ms message: 'load-balancer-api-external: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:50:54Z" - latency: 8.476084ms message: 'load-balancer-api-external: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:50:54Z" - latency: 5.936013ms message: 'load-balancer-api-external: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:49:54Z" - latency: 10.527496ms message: 'load-balancer-api-external: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:49:54Z" - latency: 5.208753ms message: 'load-balancer-api-external: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:48:54Z" - latency: 8.904037ms message: 'load-balancer-api-external: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:48:54Z" - latency: 3.709853ms message: 'load-balancer-api-external: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:47:54Z" - latency: 8.979454ms message: 'load-balancer-api-external: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:47:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:09:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-151-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-151.ec2.internal uid: 1ee57d4d-15ec-4a1c-8de1-22684548f4b9 resourceVersion: "31878" uid: a14794e3-446c-414e-9208-a88822ed2d9b spec: sourcePod: network-check-source-8894fc9bd-2dp7z targetEndpoint: ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T19:15:54Z" message: 'load-balancer-api-internal: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.927439ms message: 'load-balancer-api-internal: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:51:54Z" - latency: 7.854263ms message: 'load-balancer-api-internal: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:51:54Z" - latency: 4.39647ms message: 'load-balancer-api-internal: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:50:54Z" - latency: 8.440976ms message: 'load-balancer-api-internal: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:50:54Z" - latency: 6.639752ms message: 'load-balancer-api-internal: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:49:54Z" - latency: 10.515028ms message: 'load-balancer-api-internal: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:49:54Z" - latency: 5.170825ms message: 'load-balancer-api-internal: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:48:54Z" - latency: 9.028831ms message: 'load-balancer-api-internal: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:48:54Z" - latency: 3.721651ms message: 'load-balancer-api-internal: tcp connection to ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:47:54Z" - latency: 9.026983ms message: 'load-balancer-api-internal: resolved host name ae852d6335a37450db04c60e66fa4405-5d2ea31de3b0cf59.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T19:47:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:09:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-151-to-network-check-target-ip-10-0-129-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-151.ec2.internal uid: 1ee57d4d-15ec-4a1c-8de1-22684548f4b9 resourceVersion: "31873" uid: 3c83fed3-aa7f-4c33-bb9b-e1a875c09f4e spec: sourcePod: network-check-source-8894fc9bd-2dp7z targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:16:54Z" message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.053µs message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:51:54Z" - latency: 1.581092ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:50:54Z" - latency: 849.599µs message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:49:54Z" - latency: 885.992µs message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:48:54Z" - latency: 1.352653ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:47:54Z" - latency: 865.752µs message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:46:54Z" - latency: 843.27µs message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:45:54Z" - latency: 1.169856ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:44:54Z" - latency: 790.119µs message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:43:54Z" - latency: 1.333217ms message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:42:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:09:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-151-to-network-check-target-ip-10-0-130-85 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-151.ec2.internal uid: 1ee57d4d-15ec-4a1c-8de1-22684548f4b9 resourceVersion: "31874" uid: 29898851-f50a-4162-9ba7-6ecfefaac1f6 spec: sourcePod: network-check-source-8894fc9bd-2dp7z targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:16:54Z" message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.969645ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:51:54Z" - latency: 1.820811ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:50:54Z" - latency: 1.783822ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:49:54Z" - latency: 1.760827ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:48:54Z" - latency: 1.893903ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:47:54Z" - latency: 1.636566ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:46:54Z" - latency: 2.001201ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:45:54Z" - latency: 1.879534ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:44:54Z" - latency: 1.938957ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:43:54Z" - latency: 1.89583ms message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:42:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:09:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-151-to-network-check-target-ip-10-0-138-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-151.ec2.internal uid: 1ee57d4d-15ec-4a1c-8de1-22684548f4b9 resourceVersion: "31875" uid: 83b91df7-0cf7-4522-a17a-fcfcaea09d1c spec: sourcePod: network-check-source-8894fc9bd-2dp7z targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T19:16:54Z" message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.03264ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:51:54Z" - latency: 2.162431ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:50:54Z" - latency: 1.925917ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:49:54Z" - latency: 2.101271ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:48:54Z" - latency: 2.116707ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:47:54Z" - latency: 2.137123ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:46:54Z" - latency: 2.136778ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:45:54Z" - latency: 2.133646ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:44:54Z" - latency: 1.940251ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:43:54Z" - latency: 1.928461ms message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:42:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T19:09:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-151-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-151.ec2.internal uid: 1ee57d4d-15ec-4a1c-8de1-22684548f4b9 resourceVersion: "31876" uid: 931aa540-2ed6-4009-bf57-7c0991bb977e spec: sourcePod: network-check-source-8894fc9bd-2dp7z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T19:15:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.05µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:51:54Z" - latency: 1.4859ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:51:54Z" - latency: 1.039915ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:50:54Z" - latency: 1.802121ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:50:54Z" - latency: 957.77µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:49:54Z" - latency: 1.593496ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:49:54Z" - latency: 880.348µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:48:54Z" - latency: 1.753732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:48:54Z" - latency: 858.602µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T19:47:54Z" - latency: 1.67024ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T19:47:54Z" kind: List metadata: resourceVersion: ""