apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:47:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-110-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-110.ec2.internal uid: d48e6393-1f1a-48e3-a24e-0acc505b1108 resourceVersion: "45348" uid: 5aeeec4d-4f50-49a7-ae6c-d33d27958d54 spec: sourcePod: network-check-source-7f44b6dd87-7zrjp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T20:54:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:15:25Z" - latency: 1.169745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:14:25Z" - latency: 1.11783ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:13:25Z" - latency: 1.169571ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:12:25Z" - latency: 1.08682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:11:25Z" - latency: 1.11727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:10:25Z" - latency: 1.052556ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:09:25Z" - latency: 1.404837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:08:25Z" - latency: 1.138886ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:07:25Z" - latency: 866.833µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:47:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-110-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-110.ec2.internal uid: d48e6393-1f1a-48e3-a24e-0acc505b1108 resourceVersion: "47369" uid: 7ce4eceb-2916-4cb8-82df-aff20c8f9691 spec: sourcePod: network-check-source-7f44b6dd87-7zrjp targetEndpoint: a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T20:53:25Z" message: 'load-balancer-api-external: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.265086ms message: 'load-balancer-api-external: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:17:25Z" - latency: 6.905227ms message: 'load-balancer-api-external: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:17:25Z" - latency: 5.404416ms message: 'load-balancer-api-external: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:16:25Z" - latency: 7.205519ms message: 'load-balancer-api-external: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:16:25Z" - latency: 4.736628ms message: 'load-balancer-api-external: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:15:25Z" - latency: 7.102222ms message: 'load-balancer-api-external: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:15:25Z" - latency: 4.07269ms message: 'load-balancer-api-external: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:14:25Z" - latency: 8.542717ms message: 'load-balancer-api-external: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:14:25Z" - latency: 3.110369ms message: 'load-balancer-api-external: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:13:25Z" - latency: 7.786693ms message: 'load-balancer-api-external: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:13:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:47:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-110-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-110.ec2.internal uid: d48e6393-1f1a-48e3-a24e-0acc505b1108 resourceVersion: "47371" uid: 50c14063-c649-4e03-b08e-5c9a160a2099 spec: sourcePod: network-check-source-7f44b6dd87-7zrjp targetEndpoint: a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T20:53:25Z" message: 'load-balancer-api-internal: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.34301ms message: 'load-balancer-api-internal: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:17:25Z" - latency: 6.941961ms message: 'load-balancer-api-internal: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:17:25Z" - latency: 5.138226ms message: 'load-balancer-api-internal: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:16:25Z" - latency: 7.117982ms message: 'load-balancer-api-internal: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:16:25Z" - latency: 3.980811ms message: 'load-balancer-api-internal: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:15:25Z" - latency: 7.049536ms message: 'load-balancer-api-internal: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:15:25Z" - latency: 4.865087ms message: 'load-balancer-api-internal: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:14:25Z" - latency: 8.596334ms message: 'load-balancer-api-internal: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:14:25Z" - latency: 4.02649ms message: 'load-balancer-api-internal: tcp connection to a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:13:25Z" - latency: 7.759379ms message: 'load-balancer-api-internal: resolved host name a0cc1fb107a0540bdb2191f2fee08f5c-9beb364cbd0d2a7d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T21:13:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:47:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-110-to-network-check-target-ip-10-0-131-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-110.ec2.internal uid: d48e6393-1f1a-48e3-a24e-0acc505b1108 resourceVersion: "45346" uid: cef4a5fa-f1cb-41d2-a681-d5a778aa7e62 spec: sourcePod: network-check-source-7f44b6dd87-7zrjp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T20:54:25Z" message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.089642ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:15:25Z" - latency: 2.129857ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:14:25Z" - latency: 2.139293ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:13:25Z" - latency: 2.243482ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:12:25Z" - latency: 2.223006ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:11:25Z" - latency: 2.181293ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:10:25Z" - latency: 2.2603ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:09:25Z" - latency: 2.45841ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:08:25Z" - latency: 2.131567ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:07:25Z" - latency: 2.271973ms message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:47:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-110-to-network-check-target-ip-10-0-132-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-110.ec2.internal uid: d48e6393-1f1a-48e3-a24e-0acc505b1108 resourceVersion: "45344" uid: 61758051-430f-45ab-894e-c892b8bae5e1 spec: sourcePod: network-check-source-7f44b6dd87-7zrjp targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T20:54:25Z" message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.766581ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:15:25Z" - latency: 1.930388ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:14:25Z" - latency: 1.946191ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:13:25Z" - latency: 1.850728ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:12:25Z" - latency: 2.076959ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:11:25Z" - latency: 1.732607ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:10:25Z" - latency: 2.090591ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:09:25Z" - latency: 1.884626ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:08:25Z" - latency: 2.141019ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:07:25Z" - latency: 1.681509ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:47:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-110-to-network-check-target-ip-10-0-133-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-110.ec2.internal uid: d48e6393-1f1a-48e3-a24e-0acc505b1108 resourceVersion: "45345" uid: ee53cb2f-b37d-4075-be84-19815ac94fdb spec: sourcePod: network-check-source-7f44b6dd87-7zrjp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T20:54:25Z" message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.226173ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:15:25Z" - latency: 1.230062ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:14:25Z" - latency: 924.749µs message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:13:25Z" - latency: 840.556µs message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:12:25Z" - latency: 891.603µs message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:11:25Z" - latency: 795.385µs message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:10:25Z" - latency: 849.412µs message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:09:25Z" - latency: 1.236708ms message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:08:25Z" - latency: 884.785µs message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:07:25Z" - latency: 893.252µs message: 'network-check-target-ip-10-0-133-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T20:47:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-110-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-110.ec2.internal uid: d48e6393-1f1a-48e3-a24e-0acc505b1108 resourceVersion: "47367" uid: 980a6eda-6a49-427a-8b1e-4f670f584601 spec: sourcePod: network-check-source-7f44b6dd87-7zrjp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T20:53:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.602µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:17:25Z" - latency: 1.704889ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:17:25Z" - latency: 962.467µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:16:25Z" - latency: 2.028044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:16:25Z" - latency: 1.169558ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:15:25Z" - latency: 1.52263ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:15:25Z" - latency: 886.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:14:25Z" - latency: 1.817049ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:14:25Z" - latency: 935.129µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T21:13:25Z" - latency: 1.854508ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T21:13:25Z" kind: List metadata: resourceVersion: ""