apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: c45e8137-a6d9-4177-8183-f248a30d24e7 resourceVersion: "22712" uid: e82fa4f9-91af-4201-af30-d2f51a019d52 spec: sourcePod: network-check-source-685456655f-5xms5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T16:13:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.306449ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:13:23Z" - latency: 1.399961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:12:23Z" - latency: 1.086327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:11:23Z" - latency: 1.601655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:10:23Z" - latency: 1.277855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:09:23Z" - latency: 1.046418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:08:23Z" - latency: 1.113148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:07:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: c45e8137-a6d9-4177-8183-f248a30d24e7 resourceVersion: "21395" uid: 3d7ebb47-0754-4a58-9cca-c88bf815999b spec: sourcePod: network-check-source-685456655f-5xms5 targetEndpoint: ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T16:12:23Z" message: 'load-balancer-api-external: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.675317ms message: 'load-balancer-api-external: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:12:23Z" - latency: 7.940053ms message: 'load-balancer-api-external: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:12:23Z" - latency: 6.651354ms message: 'load-balancer-api-external: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:11:23Z" - latency: 6.767479ms message: 'load-balancer-api-external: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:11:23Z" - latency: 5.24346ms message: 'load-balancer-api-external: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:10:23Z" - latency: 9.130738ms message: 'load-balancer-api-external: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:10:23Z" - latency: 4.643508ms message: 'load-balancer-api-external: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:09:23Z" - latency: 6.896077ms message: 'load-balancer-api-external: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:09:23Z" - latency: 4.447359ms message: 'load-balancer-api-external: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:08:23Z" - latency: 6.48644ms message: 'load-balancer-api-external: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: c45e8137-a6d9-4177-8183-f248a30d24e7 resourceVersion: "21396" uid: 4e6372e0-78e8-4134-b940-30329eaacab8 spec: sourcePod: network-check-source-685456655f-5xms5 targetEndpoint: ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T16:12:23Z" message: 'load-balancer-api-internal: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.17365ms message: 'load-balancer-api-internal: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:12:23Z" - latency: 8.007144ms message: 'load-balancer-api-internal: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:12:23Z" - latency: 6.712913ms message: 'load-balancer-api-internal: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:11:23Z" - latency: 6.856327ms message: 'load-balancer-api-internal: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:11:23Z" - latency: 5.258183ms message: 'load-balancer-api-internal: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:10:23Z" - latency: 9.058152ms message: 'load-balancer-api-internal: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:10:23Z" - latency: 4.654027ms message: 'load-balancer-api-internal: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:09:23Z" - latency: 6.984729ms message: 'load-balancer-api-internal: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:09:23Z" - latency: 4.418965ms message: 'load-balancer-api-internal: tcp connection to ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:08:23Z" - latency: 6.555165ms message: 'load-balancer-api-internal: resolved host name ab35007ad3f504b8993c6262acc5ef50-1ba839fec70c45da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T16:08:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-network-check-target-ip-10-0-135-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: c45e8137-a6d9-4177-8183-f248a30d24e7 resourceVersion: "22711" uid: dbd40813-1557-4ac2-a39f-dffeb3028085 spec: sourcePod: network-check-source-685456655f-5xms5 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T16:13:23Z" message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.46003ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:13:23Z" - latency: 2.878967ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:12:23Z" - latency: 2.259149ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:11:23Z" - latency: 2.3192ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:10:23Z" - latency: 2.355664ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:09:23Z" - latency: 2.309188ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:08:23Z" - latency: 2.469651ms message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:07:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-network-check-target-ip-10-0-135-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: c45e8137-a6d9-4177-8183-f248a30d24e7 resourceVersion: "22709" uid: 57fe9b55-bdf5-44ea-b60f-85a266e76b0e spec: sourcePod: network-check-source-685456655f-5xms5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T16:13:23Z" message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 996.981µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:13:23Z" - latency: 864.445µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:12:23Z" - latency: 1.572805ms message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:11:23Z" - latency: 1.037501ms message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:10:23Z" - latency: 898.817µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:09:23Z" - latency: 851.844µs message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:08:23Z" - latency: 1.618635ms message: 'network-check-target-ip-10-0-135-53: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:07:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-network-check-target-ip-10-0-135-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: c45e8137-a6d9-4177-8183-f248a30d24e7 resourceVersion: "22710" uid: af5baba8-fca7-472b-a7a2-8d51f6edfc6e spec: sourcePod: network-check-source-685456655f-5xms5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-10T16:13:23Z" message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.617457ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:13:23Z" - latency: 2.232449ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:12:23Z" - latency: 2.418305ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:11:23Z" - latency: 2.319783ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:10:23Z" - latency: 2.246531ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:09:23Z" - latency: 1.995545ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:08:23Z" - latency: 2.765387ms message: 'network-check-target-ip-10-0-135-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:07:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T16:06:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-53-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-53.ec2.internal uid: c45e8137-a6d9-4177-8183-f248a30d24e7 resourceVersion: "21394" uid: 0309658e-21e0-4e74-92fc-d7055e26a13e spec: sourcePod: network-check-source-685456655f-5xms5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T16:12:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.182092ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:12:23Z" - latency: 1.763014ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:12:23Z" - latency: 1.040121ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:11:23Z" - latency: 1.910081ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:11:23Z" - latency: 1.269152ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:10:23Z" - latency: 1.804868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:10:23Z" - latency: 820.699µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:09:23Z" - latency: 1.699976ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:09:23Z" - latency: 994.403µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T16:08:23Z" - latency: 1.808753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T16:08:23Z" kind: List metadata: resourceVersion: ""