apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-224-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-224.ec2.internal uid: bae16180-6d5f-4616-967c-a1392a4aef9c resourceVersion: "32445" uid: 042b2283-4e43-4d9d-96f2-68325b6e6004 spec: sourcePod: network-check-source-8894fc9bd-vlg7t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T08:05:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 919.094µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:40:27Z" - latency: 1.00873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:39:27Z" - latency: 890.427µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:38:27Z" - latency: 1.171529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:37:27Z" - latency: 1.275188ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:36:27Z" - latency: 1.152449ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:35:27Z" - latency: 1.58804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:34:27Z" - latency: 1.097175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:33:27Z" - latency: 812.425µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:32:27Z" - latency: 996.66µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:31:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-224-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-224.ec2.internal uid: bae16180-6d5f-4616-967c-a1392a4aef9c resourceVersion: "32447" uid: 3b38382b-dcdb-4a05-8c03-1c1e663a5d0d spec: sourcePod: network-check-source-8894fc9bd-vlg7t targetEndpoint: ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T08:04:27Z" message: 'load-balancer-api-external: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.013219ms message: 'load-balancer-api-external: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:40:27Z" - latency: 8.567039ms message: 'load-balancer-api-external: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:40:27Z" - latency: 4.348545ms message: 'load-balancer-api-external: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:39:27Z" - latency: 6.32985ms message: 'load-balancer-api-external: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:39:27Z" - latency: 4.243699ms message: 'load-balancer-api-external: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:38:27Z" - latency: 6.523449ms message: 'load-balancer-api-external: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:38:27Z" - latency: 5.325222ms message: 'load-balancer-api-external: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:37:27Z" - latency: 10.298715ms message: 'load-balancer-api-external: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:37:27Z" - latency: 4.948175ms message: 'load-balancer-api-external: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:36:27Z" - latency: 7.584494ms message: 'load-balancer-api-external: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:36:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-224-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-224.ec2.internal uid: bae16180-6d5f-4616-967c-a1392a4aef9c resourceVersion: "32446" uid: c3a2be2d-0e32-4936-b3c6-1bc8da4cdb34 spec: sourcePod: network-check-source-8894fc9bd-vlg7t targetEndpoint: ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T08:04:27Z" message: 'load-balancer-api-internal: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.236477ms message: 'load-balancer-api-internal: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:40:27Z" - latency: 8.627728ms message: 'load-balancer-api-internal: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:40:27Z" - latency: 4.318563ms message: 'load-balancer-api-internal: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:39:27Z" - latency: 6.368153ms message: 'load-balancer-api-internal: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:39:27Z" - latency: 4.253257ms message: 'load-balancer-api-internal: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:38:27Z" - latency: 6.550362ms message: 'load-balancer-api-internal: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:38:27Z" - latency: 5.346819ms message: 'load-balancer-api-internal: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:37:27Z" - latency: 10.275044ms message: 'load-balancer-api-internal: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:37:27Z" - latency: 4.991717ms message: 'load-balancer-api-internal: tcp connection to ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:36:27Z" - latency: 7.566522ms message: 'load-balancer-api-internal: resolved host name ad1188bbbe14a4584b07754e4fe54f56-13283f3c11afe42e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T08:36:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-224-to-network-check-target-ip-10-0-137-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-224.ec2.internal uid: bae16180-6d5f-4616-967c-a1392a4aef9c resourceVersion: "32441" uid: 76d37597-0811-431c-9ffd-8bb3c181be5e spec: sourcePod: network-check-source-8894fc9bd-vlg7t targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:05:27Z" message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.962584ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:40:27Z" - latency: 1.919552ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:39:27Z" - latency: 1.616907ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:38:27Z" - latency: 1.874422ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:37:27Z" - latency: 1.683384ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:36:27Z" - latency: 2.321511ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:35:27Z" - latency: 1.914406ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:34:27Z" - latency: 1.820288ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:33:27Z" - latency: 1.86934ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:32:27Z" - latency: 1.723148ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:31:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-224-to-network-check-target-ip-10-0-138-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-224.ec2.internal uid: bae16180-6d5f-4616-967c-a1392a4aef9c resourceVersion: "32443" uid: 5f028b7e-4170-49c7-a54f-15042d31297a spec: sourcePod: network-check-source-8894fc9bd-vlg7t targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:05:27Z" message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.007524ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:40:27Z" - latency: 2.139955ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:39:27Z" - latency: 1.897356ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:38:27Z" - latency: 2.24081ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:37:27Z" - latency: 2.072582ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:36:27Z" - latency: 2.023837ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:35:27Z" - latency: 2.358ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:34:27Z" - latency: 1.964824ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:33:27Z" - latency: 1.979043ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:32:27Z" - latency: 1.891152ms message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:31:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-224-to-network-check-target-ip-10-0-141-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-224.ec2.internal uid: bae16180-6d5f-4616-967c-a1392a4aef9c resourceVersion: "32442" uid: ec9c94d4-7781-4f69-b71f-186aa4b1884e spec: sourcePod: network-check-source-8894fc9bd-vlg7t targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T08:05:27Z" message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.208095ms message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:40:27Z" - latency: 1.250984ms message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:39:27Z" - latency: 852.425µs message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:38:27Z" - latency: 940.08µs message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:37:27Z" - latency: 831.139µs message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:36:27Z" - latency: 712.726µs message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:35:27Z" - latency: 682.891µs message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:34:27Z" - latency: 1.002852ms message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:33:27Z" - latency: 783.085µs message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:32:27Z" - latency: 1.266066ms message: 'network-check-target-ip-10-0-141-224: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:31:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T07:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-224-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-224.ec2.internal uid: bae16180-6d5f-4616-967c-a1392a4aef9c resourceVersion: "32444" uid: d0dc572c-17f1-4267-951f-7660dd5f5b8c spec: sourcePod: network-check-source-8894fc9bd-vlg7t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T08:04:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 745.091µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:40:27Z" - latency: 1.926774ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:40:27Z" - latency: 1.001458ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:39:27Z" - latency: 1.767085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:39:27Z" - latency: 795.796µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:38:27Z" - latency: 1.887686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:38:27Z" - latency: 890.575µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:37:27Z" - latency: 1.875375ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:37:27Z" - latency: 748.004µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T08:36:27Z" - latency: 1.654829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T08:36:27Z" kind: List metadata: resourceVersion: ""