apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-177-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-177.ec2.internal uid: d4cdba17-1ebd-4872-8143-d94f3feaef7b resourceVersion: "32298" uid: bc5ff8ea-090a-46e7-bfde-58847505e549 spec: sourcePod: network-check-source-7cbc45fddc-99d9m targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T19:16:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.041056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:51:27Z" - latency: 1.036022ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:50:27Z" - latency: 1.044446ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:49:27Z" - latency: 1.580235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:48:27Z" - latency: 1.077759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:47:27Z" - latency: 1.030698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:46:27Z" - latency: 985.258µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:45:27Z" - latency: 1.002462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:44:27Z" - latency: 1.194451ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:43:27Z" - latency: 904.932µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:42:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-177-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-177.ec2.internal uid: d4cdba17-1ebd-4872-8143-d94f3feaef7b resourceVersion: "32300" uid: 2acd36de-7fee-44b6-8640-8344834ca193 spec: sourcePod: network-check-source-7cbc45fddc-99d9m targetEndpoint: a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T19:15:27Z" message: 'load-balancer-api-external: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.308564ms message: 'load-balancer-api-external: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:51:27Z" - latency: 8.793005ms message: 'load-balancer-api-external: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:51:27Z" - latency: 6.005853ms message: 'load-balancer-api-external: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:50:27Z" - latency: 7.090088ms message: 'load-balancer-api-external: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:50:27Z" - latency: 4.706618ms message: 'load-balancer-api-external: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:49:27Z" - latency: 7.521537ms message: 'load-balancer-api-external: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:49:27Z" - latency: 6.27299ms message: 'load-balancer-api-external: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:48:27Z" - latency: 7.659152ms message: 'load-balancer-api-external: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:48:27Z" - latency: 4.840444ms message: 'load-balancer-api-external: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:47:27Z" - latency: 7.181773ms message: 'load-balancer-api-external: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-177-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-177.ec2.internal uid: d4cdba17-1ebd-4872-8143-d94f3feaef7b resourceVersion: "32299" uid: acbc6265-5e4e-46ca-88b8-21a46febff13 spec: sourcePod: network-check-source-7cbc45fddc-99d9m targetEndpoint: a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T19:15:27Z" message: 'load-balancer-api-internal: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.236641ms message: 'load-balancer-api-internal: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:51:27Z" - latency: 8.882869ms message: 'load-balancer-api-internal: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:51:27Z" - latency: 6.010599ms message: 'load-balancer-api-internal: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:50:27Z" - latency: 7.042992ms message: 'load-balancer-api-internal: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:50:27Z" - latency: 4.790229ms message: 'load-balancer-api-internal: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:49:27Z" - latency: 7.569137ms message: 'load-balancer-api-internal: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:49:27Z" - latency: 6.32048ms message: 'load-balancer-api-internal: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:48:27Z" - latency: 7.639171ms message: 'load-balancer-api-internal: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:48:27Z" - latency: 4.28213ms message: 'load-balancer-api-internal: tcp connection to a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:47:27Z" - latency: 7.235921ms message: 'load-balancer-api-internal: resolved host name a20ba3f99a359462bb01a3feae622901-e369e1659974d558.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-177-to-network-check-target-ip-10-0-128-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-177.ec2.internal uid: d4cdba17-1ebd-4872-8143-d94f3feaef7b resourceVersion: "32294" uid: 80493033-4336-4e11-b4b8-c91b0631e081 spec: sourcePod: network-check-source-7cbc45fddc-99d9m targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T19:16:27Z" message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.103965ms message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:51:27Z" - latency: 1.020081ms message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:50:27Z" - latency: 998.023µs message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:49:27Z" - latency: 1.085193ms message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:48:27Z" - latency: 1.044353ms message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:47:27Z" - latency: 1.280467ms message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:46:27Z" - latency: 1.092115ms message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:45:27Z" - latency: 988.101µs message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:44:27Z" - latency: 1.350608ms message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:43:27Z" - latency: 888.457µs message: 'network-check-target-ip-10-0-128-177: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:42:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-177-to-network-check-target-ip-10-0-135-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-177.ec2.internal uid: d4cdba17-1ebd-4872-8143-d94f3feaef7b resourceVersion: "32295" uid: f704013e-3842-43e2-8b82-7ceec69de2c3 spec: sourcePod: network-check-source-7cbc45fddc-99d9m targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T19:16:27Z" message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.050653ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:51:27Z" - latency: 1.99946ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:50:27Z" - latency: 2.17824ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:49:27Z" - latency: 2.442501ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:48:27Z" - latency: 2.206022ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:47:27Z" - latency: 1.891399ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:46:27Z" - latency: 1.826976ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:45:27Z" - latency: 2.230016ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:44:27Z" - latency: 2.1163ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:43:27Z" - latency: 2.001033ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:42:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-177-to-network-check-target-ip-10-0-143-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-177.ec2.internal uid: d4cdba17-1ebd-4872-8143-d94f3feaef7b resourceVersion: "32296" uid: aacf4caf-93f9-462f-a1be-3dd5a529ef26 spec: sourcePod: network-check-source-7cbc45fddc-99d9m targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T19:16:27Z" message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.315419ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:51:27Z" - latency: 2.07625ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:50:27Z" - latency: 2.041522ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:49:27Z" - latency: 2.368737ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:48:27Z" - latency: 2.230066ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:47:27Z" - latency: 1.978942ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:46:27Z" - latency: 2.176466ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:45:27Z" - latency: 2.060303ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:44:27Z" - latency: 2.157138ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:43:27Z" - latency: 2.18547ms message: 'network-check-target-ip-10-0-143-217: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:42:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T19:09:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-177-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-177.ec2.internal uid: d4cdba17-1ebd-4872-8143-d94f3feaef7b resourceVersion: "32297" uid: 952793b1-4115-4c7c-ab48-c2e0352334cc spec: sourcePod: network-check-source-7cbc45fddc-99d9m targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T19:15:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.098535ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:51:27Z" - latency: 1.964272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:51:27Z" - latency: 1.035103ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:50:27Z" - latency: 1.722531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:50:27Z" - latency: 1.016258ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:49:27Z" - latency: 1.897419ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:49:27Z" - latency: 1.046882ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:48:27Z" - latency: 2.261032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:48:27Z" - latency: 1.191219ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:47:27Z" - latency: 1.776547ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:47:27Z" kind: List metadata: resourceVersion: ""