apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-93-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-93.ec2.internal uid: 24e23e83-cc19-4132-b68b-bd8cd513f8d5 resourceVersion: "32499" uid: 8c285e71-4476-40a2-9432-6bee7bbe3a8b spec: sourcePod: network-check-source-7b678d77c7-mht57 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T16:33:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 821.72µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:15:59Z" - latency: 1.434188ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:59Z" - latency: 937.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:13:59Z" - latency: 1.351954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:12:59Z" - latency: 890.284µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:59Z" - latency: 929.846µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:59Z" - latency: 1.129527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:09:59Z" - latency: 1.499019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:08:59Z" - latency: 1.017611ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:59Z" - latency: 1.392386ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-93-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-93.ec2.internal uid: 24e23e83-cc19-4132-b68b-bd8cd513f8d5 resourceVersion: "34516" uid: b8de0614-e2cc-4cc6-9c01-bc0043789763 spec: sourcePod: network-check-source-7b678d77c7-mht57 targetEndpoint: a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:32:59Z" message: 'load-balancer-api-external: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.457447ms message: 'load-balancer-api-external: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:20:59Z" - latency: 9.784021ms message: 'load-balancer-api-external: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:20:59Z" - latency: 4.651959ms message: 'load-balancer-api-external: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:19:59Z" - latency: 9.059575ms message: 'load-balancer-api-external: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:19:59Z" - latency: 4.515221ms message: 'load-balancer-api-external: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:18:59Z" - latency: 7.27217ms message: 'load-balancer-api-external: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:18:59Z" - latency: 4.521909ms message: 'load-balancer-api-external: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:17:59Z" - latency: 12.461222ms message: 'load-balancer-api-external: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:17:59Z" - latency: 5.220389ms message: 'load-balancer-api-external: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:16:59Z" - latency: 14.014221ms message: 'load-balancer-api-external: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:16:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-93-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-93.ec2.internal uid: 24e23e83-cc19-4132-b68b-bd8cd513f8d5 resourceVersion: "34517" uid: 26fadcee-9a1d-47a5-a510-8a3d7b1b1a4d spec: sourcePod: network-check-source-7b678d77c7-mht57 targetEndpoint: a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:32:59Z" message: 'load-balancer-api-internal: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.575291ms message: 'load-balancer-api-internal: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:20:59Z" - latency: 9.712095ms message: 'load-balancer-api-internal: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:20:59Z" - latency: 4.420887ms message: 'load-balancer-api-internal: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:19:59Z" - latency: 8.978353ms message: 'load-balancer-api-internal: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:19:59Z" - latency: 4.483597ms message: 'load-balancer-api-internal: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:18:59Z" - latency: 7.174651ms message: 'load-balancer-api-internal: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:18:59Z" - latency: 4.48582ms message: 'load-balancer-api-internal: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:17:59Z" - latency: 12.41048ms message: 'load-balancer-api-internal: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:17:59Z" - latency: 5.233458ms message: 'load-balancer-api-internal: tcp connection to a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:16:59Z" - latency: 13.964544ms message: 'load-balancer-api-internal: resolved host name a1e38873a8b6349c19950de410b47630-f3f6ad7d36676144.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:16:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-93-to-network-check-target-ip-10-0-128-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-93.ec2.internal uid: 24e23e83-cc19-4132-b68b-bd8cd513f8d5 resourceVersion: "32497" uid: b9e08205-54e5-4ca0-9343-746634f091bd spec: sourcePod: network-check-source-7b678d77c7-mht57 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:33:59Z" message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.171088ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:15:59Z" - latency: 2.369934ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:59Z" - latency: 2.351642ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:59Z" - latency: 2.92127ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:12:59Z" - latency: 2.417961ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:59Z" - latency: 2.361476ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:59Z" - latency: 2.403704ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:09:59Z" - latency: 2.271829ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:08:59Z" - latency: 2.986185ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:59Z" - latency: 2.287131ms message: 'network-check-target-ip-10-0-128-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-93-to-network-check-target-ip-10-0-128-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-93.ec2.internal uid: 24e23e83-cc19-4132-b68b-bd8cd513f8d5 resourceVersion: "32498" uid: 4a05e0f0-5809-42af-b960-d3254d160612 spec: sourcePod: network-check-source-7b678d77c7-mht57 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:33:59Z" message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.133211ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:15:59Z" - latency: 2.186516ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:59Z" - latency: 2.290176ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:59Z" - latency: 2.370475ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:12:59Z" - latency: 2.505269ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:59Z" - latency: 1.969117ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:59Z" - latency: 2.260839ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:09:59Z" - latency: 2.291984ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:08:59Z" - latency: 2.087554ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:59Z" - latency: 2.286252ms message: 'network-check-target-ip-10-0-128-64: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-93-to-network-check-target-ip-10-0-141-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-93.ec2.internal uid: 24e23e83-cc19-4132-b68b-bd8cd513f8d5 resourceVersion: "32496" uid: 0e0445f0-6e66-4804-80c1-21bf253c1409 spec: sourcePod: network-check-source-7b678d77c7-mht57 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:33:59Z" message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.197507ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:15:59Z" - latency: 1.963202ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:59Z" - latency: 1.028114ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:59Z" - latency: 1.59994ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:12:59Z" - latency: 841.744µs message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:11:59Z" - latency: 1.198811ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:10:59Z" - latency: 1.233645ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:09:59Z" - latency: 978.77µs message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:08:59Z" - latency: 992.798µs message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:07:59Z" - latency: 1.377823ms message: 'network-check-target-ip-10-0-141-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:06:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-93-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-93.ec2.internal uid: 24e23e83-cc19-4132-b68b-bd8cd513f8d5 resourceVersion: "34514" uid: 8d96ea9e-7553-4475-9b9a-2101b1559fc8 spec: sourcePod: network-check-source-7b678d77c7-mht57 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T16:32:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.556µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:20:59Z" - latency: 1.827554ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:20:59Z" - latency: 991.579µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:19:59Z" - latency: 1.529381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:19:59Z" - latency: 1.109403ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:18:59Z" - latency: 1.688237ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:18:59Z" - latency: 1.240055ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:17:59Z" - latency: 2.078422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:17:59Z" - latency: 859.026µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:16:59Z" - latency: 1.82988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:16:59Z" kind: List metadata: resourceVersion: ""