apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:01:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-88-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-88.ec2.internal uid: 3569ec9c-6040-43bc-b73b-8a82c7ab8126 resourceVersion: "44230" uid: 5c0e0cca-58eb-4d5e-bc87-73a20045eb96 spec: sourcePod: network-check-source-dbd9cf844-wpkw4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T12:08:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.190961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:29:13Z" - latency: 1.406309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:28:13Z" - latency: 857.72µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:27:13Z" - latency: 1.100508ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:26:13Z" - latency: 1.514059ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:25:13Z" - latency: 1.13928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:24:13Z" - latency: 895.634µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:23:13Z" - latency: 1.050541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:22:13Z" - latency: 1.281265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:21:13Z" - latency: 1.463568ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:20:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:01:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-88-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-88.ec2.internal uid: 3569ec9c-6040-43bc-b73b-8a82c7ab8126 resourceVersion: "46383" uid: d1463443-93a6-46a6-980f-aaf6a987d2fd spec: sourcePod: network-check-source-dbd9cf844-wpkw4 targetEndpoint: abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T12:07:13Z" message: 'load-balancer-api-external: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.753358ms message: 'load-balancer-api-external: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:31:13Z" - latency: 9.076256ms message: 'load-balancer-api-external: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:31:13Z" - latency: 3.570049ms message: 'load-balancer-api-external: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:30:13Z" - latency: 10.303945ms message: 'load-balancer-api-external: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:30:13Z" - latency: 8.402976ms message: 'load-balancer-api-external: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:29:13Z" - latency: 8.631136ms message: 'load-balancer-api-external: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:29:13Z" - latency: 5.972841ms message: 'load-balancer-api-external: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:28:13Z" - latency: 8.904651ms message: 'load-balancer-api-external: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:28:13Z" - latency: 6.022599ms message: 'load-balancer-api-external: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:27:13Z" - latency: 8.307754ms message: 'load-balancer-api-external: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:27:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:01:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-88-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-88.ec2.internal uid: 3569ec9c-6040-43bc-b73b-8a82c7ab8126 resourceVersion: "46382" uid: 7ec5faca-aaf8-4c62-a694-d76a9c90c473 spec: sourcePod: network-check-source-dbd9cf844-wpkw4 targetEndpoint: abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T12:07:13Z" message: 'load-balancer-api-internal: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.659642ms message: 'load-balancer-api-internal: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:31:13Z" - latency: 9.113306ms message: 'load-balancer-api-internal: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:31:13Z" - latency: 3.584897ms message: 'load-balancer-api-internal: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:30:13Z" - latency: 10.275012ms message: 'load-balancer-api-internal: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:30:13Z" - latency: 5.039079ms message: 'load-balancer-api-internal: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:29:13Z" - latency: 8.679628ms message: 'load-balancer-api-internal: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:29:13Z" - latency: 6.211087ms message: 'load-balancer-api-internal: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:28:13Z" - latency: 8.940761ms message: 'load-balancer-api-internal: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:28:13Z" - latency: 3.99812ms message: 'load-balancer-api-internal: tcp connection to abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:27:13Z" - latency: 8.346344ms message: 'load-balancer-api-internal: resolved host name abd85b32872364bf5947a353f25fafca-b53f8b7af3d1992e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T12:27:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:01:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-88-to-network-check-target-ip-10-0-128-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-88.ec2.internal uid: 3569ec9c-6040-43bc-b73b-8a82c7ab8126 resourceVersion: "44227" uid: a5861eda-bf82-464d-bf5f-2ee3bc387c56 spec: sourcePod: network-check-source-dbd9cf844-wpkw4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:08:13Z" message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.099806ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:29:13Z" - latency: 1.513897ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:28:13Z" - latency: 1.385352ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:27:13Z" - latency: 1.415799ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:26:13Z" - latency: 1.352951ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:25:13Z" - latency: 753.317µs message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:24:13Z" - latency: 848.813µs message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:23:13Z" - latency: 968.54µs message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:22:13Z" - latency: 1.185886ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:21:13Z" - latency: 1.343315ms message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:20:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:01:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-88-to-network-check-target-ip-10-0-131-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-88.ec2.internal uid: 3569ec9c-6040-43bc-b73b-8a82c7ab8126 resourceVersion: "44229" uid: 1a405f33-e32f-4537-92e2-6ff60c678819 spec: sourcePod: network-check-source-dbd9cf844-wpkw4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:08:13Z" message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.373793ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:29:13Z" - latency: 2.364009ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:28:13Z" - latency: 2.257662ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:27:13Z" - latency: 2.406798ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:26:13Z" - latency: 2.355402ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:25:13Z" - latency: 2.365899ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:24:13Z" - latency: 2.424479ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:23:13Z" - latency: 2.462834ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:22:13Z" - latency: 2.507768ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:21:13Z" - latency: 2.346489ms message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:20:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:01:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-88-to-network-check-target-ip-10-0-139-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-88.ec2.internal uid: 3569ec9c-6040-43bc-b73b-8a82c7ab8126 resourceVersion: "44228" uid: 5b3a5062-8c46-44cd-9716-979607147224 spec: sourcePod: network-check-source-dbd9cf844-wpkw4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-10T12:08:13Z" message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.1775ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:29:13Z" - latency: 1.988945ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:28:13Z" - latency: 1.700955ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:27:13Z" - latency: 2.066954ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:26:13Z" - latency: 2.16079ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:25:13Z" - latency: 2.131006ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:24:13Z" - latency: 2.111141ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:23:13Z" - latency: 2.117577ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:22:13Z" - latency: 2.068541ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:21:13Z" - latency: 2.319103ms message: 'network-check-target-ip-10-0-139-86: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:20:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T12:01:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-88-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-88.ec2.internal uid: 3569ec9c-6040-43bc-b73b-8a82c7ab8126 resourceVersion: "46381" uid: 94963755-83b4-49f1-bae3-1573accea0d4 spec: sourcePod: network-check-source-dbd9cf844-wpkw4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T12:07:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.856µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:31:13Z" - latency: 1.80551ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:31:13Z" - latency: 1.191456ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:30:13Z" - latency: 1.950307ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:30:13Z" - latency: 954.238µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:29:13Z" - latency: 2.091512ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:29:13Z" - latency: 1.265982ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:28:13Z" - latency: 1.938822ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:28:13Z" - latency: 1.102626ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T12:27:13Z" - latency: 1.972808ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T12:27:13Z" kind: List metadata: resourceVersion: ""