apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:45:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: a0073629-e2c7-422e-9cc0-466d8edd7c30 resourceVersion: "18609" uid: 65bc3470-7e3f-43e2-bd2a-8066658f1c3d spec: sourcePod: network-check-source-7b678d77c7-zll94 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T17:52:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.003227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:59:57Z" - latency: 885.987µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:58:57Z" - latency: 1.147086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:57:57Z" - latency: 1.034675ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:56:57Z" - latency: 864.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:55:57Z" - latency: 852.37µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:54:57Z" - latency: 999.217µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:53:57Z" - latency: 1.180331ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:52:57Z" - latency: 1.093626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:51:57Z" - latency: 1.031797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:50:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:45:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: a0073629-e2c7-422e-9cc0-466d8edd7c30 resourceVersion: "17625" uid: d95eb045-0d05-4478-bfee-53e29c99f6ad spec: sourcePod: network-check-source-7b678d77c7-zll94 targetEndpoint: ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T17:51:57Z" message: 'load-balancer-api-external: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.023867ms message: 'load-balancer-api-external: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:57:57Z" - latency: 8.464402ms message: 'load-balancer-api-external: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:57:57Z" - latency: 4.172258ms message: 'load-balancer-api-external: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:56:57Z" - latency: 8.126355ms message: 'load-balancer-api-external: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:56:57Z" - latency: 4.223745ms message: 'load-balancer-api-external: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:55:57Z" - latency: 8.043962ms message: 'load-balancer-api-external: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:55:57Z" - latency: 4.462844ms message: 'load-balancer-api-external: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:54:57Z" - latency: 8.057729ms message: 'load-balancer-api-external: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:54:57Z" - latency: 4.444703ms message: 'load-balancer-api-external: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:53:57Z" - latency: 8.14107ms message: 'load-balancer-api-external: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:53:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:45:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: a0073629-e2c7-422e-9cc0-466d8edd7c30 resourceVersion: "17624" uid: e52638c4-11f1-4425-91f2-f50fe6111de7 spec: sourcePod: network-check-source-7b678d77c7-zll94 targetEndpoint: ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T17:51:57Z" message: 'load-balancer-api-internal: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.187505ms message: 'load-balancer-api-internal: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:57:57Z" - latency: 8.581901ms message: 'load-balancer-api-internal: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:57:57Z" - latency: 4.167469ms message: 'load-balancer-api-internal: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:56:57Z" - latency: 8.143666ms message: 'load-balancer-api-internal: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:56:57Z" - latency: 4.665188ms message: 'load-balancer-api-internal: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:55:57Z" - latency: 7.972744ms message: 'load-balancer-api-internal: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:55:57Z" - latency: 4.962744ms message: 'load-balancer-api-internal: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:54:57Z" - latency: 8.041737ms message: 'load-balancer-api-internal: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:54:57Z" - latency: 4.50063ms message: 'load-balancer-api-internal: tcp connection to ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:53:57Z" - latency: 8.075596ms message: 'load-balancer-api-internal: resolved host name ae06791d4888f49c08b4718ac869599a-dceecf3703135048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:53:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:45:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-network-check-target-ip-10-0-138-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: a0073629-e2c7-422e-9cc0-466d8edd7c30 resourceVersion: "18608" uid: a04b0190-a82a-4c75-9856-0a0c9f1d1971 spec: sourcePod: network-check-source-7b678d77c7-zll94 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:52:57Z" message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.328328ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:59:57Z" - latency: 1.793863ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:58:57Z" - latency: 1.712723ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:57:57Z" - latency: 2.359652ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:56:57Z" - latency: 2.143768ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:55:57Z" - latency: 2.213324ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:54:57Z" - latency: 2.431353ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:53:57Z" - latency: 2.00285ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:52:57Z" - latency: 2.412825ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:51:57Z" - latency: 2.214902ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:50:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:45:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-network-check-target-ip-10-0-140-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: a0073629-e2c7-422e-9cc0-466d8edd7c30 resourceVersion: "18607" uid: b4a12b2d-21fe-4383-9774-5777ef86814d spec: sourcePod: network-check-source-7b678d77c7-zll94 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:52:57Z" message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.578057ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:59:57Z" - latency: 1.590705ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:58:57Z" - latency: 1.683051ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:57:57Z" - latency: 2.083977ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:56:57Z" - latency: 1.663432ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:55:57Z" - latency: 1.816027ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:54:57Z" - latency: 1.572541ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:53:57Z" - latency: 1.539843ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:52:57Z" - latency: 1.481957ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:51:57Z" - latency: 1.657438ms message: 'network-check-target-ip-10-0-140-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:50:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:45:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-network-check-target-ip-10-0-143-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: a0073629-e2c7-422e-9cc0-466d8edd7c30 resourceVersion: "18606" uid: fe1cdbf8-bc41-48aa-94b4-46373f5c8a4c spec: sourcePod: network-check-source-7b678d77c7-zll94 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T17:52:57Z" message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.579µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:59:57Z" - latency: 1.430938ms message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:58:57Z" - latency: 864.79µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:57:57Z" - latency: 822.72µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:56:57Z" - latency: 776.028µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:55:57Z" - latency: 777.188µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:54:57Z" - latency: 1.262628ms message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:53:57Z" - latency: 1.431029ms message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:52:57Z" - latency: 1.372173ms message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:51:57Z" - latency: 785.669µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:50:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T17:45:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: a0073629-e2c7-422e-9cc0-466d8edd7c30 resourceVersion: "17623" uid: 9197d7d7-e109-4f9e-83b6-2942e46bc9d2 spec: sourcePod: network-check-source-7b678d77c7-zll94 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T17:51:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 860.11µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:57:57Z" - latency: 1.570353ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:57:57Z" - latency: 881.67µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:56:57Z" - latency: 1.599834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:56:57Z" - latency: 770.896µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:55:57Z" - latency: 1.644328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:55:57Z" - latency: 953.902µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:54:57Z" - latency: 1.525398ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:54:57Z" - latency: 836.059µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:53:57Z" - latency: 1.911208ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:53:57Z" kind: List metadata: resourceVersion: ""