apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-62-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-62.ec2.internal uid: c5440ef5-65f0-4461-b8fe-6ff18a65c6cc resourceVersion: "54841" uid: 094bcbb9-bfd9-4284-b765-a12643a01365 spec: sourcePod: network-check-source-6f78d59f99-5ks6c targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:08:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.267µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:57:51Z" - latency: 1.432886ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:56:51Z" - latency: 1.135524ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:55:51Z" - latency: 1.421542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:54:51Z" - latency: 1.366865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:53:51Z" - latency: 784.527µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:52:51Z" - latency: 1.01439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:51:51Z" - latency: 950.154µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:50:51Z" - latency: 1.119772ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:49:51Z" - latency: 1.065002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:48:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-62-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-62.ec2.internal uid: c5440ef5-65f0-4461-b8fe-6ff18a65c6cc resourceVersion: "51845" uid: 8a94433f-91c2-4fc6-a121-6c2f85b349cd spec: sourcePod: network-check-source-6f78d59f99-5ks6c targetEndpoint: a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:07:51Z" message: 'load-balancer-api-external: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 19.408589ms message: 'load-balancer-api-external: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:55:51Z" - latency: 7.346388ms message: 'load-balancer-api-external: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:55:51Z" - latency: 17.999655ms message: 'load-balancer-api-external: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:54:51Z" - latency: 6.99993ms message: 'load-balancer-api-external: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:54:51Z" - latency: 17.266767ms message: 'load-balancer-api-external: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:53:51Z" - latency: 7.059361ms message: 'load-balancer-api-external: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:53:51Z" - latency: 16.847459ms message: 'load-balancer-api-external: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:52:51Z" - latency: 7.967982ms message: 'load-balancer-api-external: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:52:51Z" - latency: 18.177005ms message: 'load-balancer-api-external: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:51:51Z" - latency: 6.953075ms message: 'load-balancer-api-external: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:51:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-62-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-62.ec2.internal uid: c5440ef5-65f0-4461-b8fe-6ff18a65c6cc resourceVersion: "51844" uid: 7e4f99fe-06a3-483e-9683-67b051ad91de spec: sourcePod: network-check-source-6f78d59f99-5ks6c targetEndpoint: a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:07:51Z" message: 'load-balancer-api-internal: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 19.366128ms message: 'load-balancer-api-internal: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:55:51Z" - latency: 7.215594ms message: 'load-balancer-api-internal: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:55:51Z" - latency: 18.567722ms message: 'load-balancer-api-internal: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:54:51Z" - latency: 7.198602ms message: 'load-balancer-api-internal: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:54:51Z" - latency: 16.604511ms message: 'load-balancer-api-internal: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:53:51Z" - latency: 7.006676ms message: 'load-balancer-api-internal: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:53:51Z" - latency: 16.26265ms message: 'load-balancer-api-internal: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:52:51Z" - latency: 8.179015ms message: 'load-balancer-api-internal: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:52:51Z" - latency: 16.058111ms message: 'load-balancer-api-internal: tcp connection to a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:51:51Z" - latency: 6.898049ms message: 'load-balancer-api-internal: resolved host name a1d10cb30bef24ef193b7775bb1c3c8c-dfe7d2fa7d2d1852.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:51:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-62-to-network-check-target-ip-10-0-131-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-62.ec2.internal uid: c5440ef5-65f0-4461-b8fe-6ff18a65c6cc resourceVersion: "54838" uid: 619a5694-27a5-4f36-9918-d6a4ccc4bc00 spec: sourcePod: network-check-source-6f78d59f99-5ks6c targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:08:51Z" message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.139028ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:57:51Z" - latency: 1.956154ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:56:51Z" - latency: 1.833139ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:55:51Z" - latency: 1.966603ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:54:51Z" - latency: 2.001497ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:53:51Z" - latency: 1.828985ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:52:51Z" - latency: 1.943922ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:51:51Z" - latency: 1.881734ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:50:51Z" - latency: 1.41428ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:49:51Z" - latency: 1.908208ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:48:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-62-to-network-check-target-ip-10-0-133-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-62.ec2.internal uid: c5440ef5-65f0-4461-b8fe-6ff18a65c6cc resourceVersion: "54837" uid: b55294f0-ec4d-414e-9242-9be0bfaafd5b spec: sourcePod: network-check-source-6f78d59f99-5ks6c targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:08:51Z" message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.344159ms message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:57:51Z" - latency: 2.470143ms message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:56:51Z" - latency: 1.247262ms message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:55:51Z" - latency: 1.783782ms message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:54:51Z" - latency: 1.085806ms message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:53:51Z" - latency: 1.521819ms message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:52:51Z" - latency: 1.380576ms message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:51:51Z" - latency: 998.218µs message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:50:51Z" - latency: 873.333µs message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:49:51Z" - latency: 1.418744ms message: 'network-check-target-ip-10-0-133-62: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:48:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-62-to-network-check-target-ip-10-0-136-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-62.ec2.internal uid: c5440ef5-65f0-4461-b8fe-6ff18a65c6cc resourceVersion: "54839" uid: dab488d4-8d78-467f-9199-c9f93a414e96 spec: sourcePod: network-check-source-6f78d59f99-5ks6c targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:08:51Z" message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.227267ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:57:51Z" - latency: 3.062241ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:56:51Z" - latency: 2.004391ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:55:51Z" - latency: 1.949768ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:54:51Z" - latency: 2.156089ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:53:51Z" - latency: 2.358208ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:52:51Z" - latency: 2.101632ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:51:51Z" - latency: 1.93712ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:50:51Z" - latency: 1.949723ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:49:51Z" - latency: 2.456777ms message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:48:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:01:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-62-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-62.ec2.internal uid: c5440ef5-65f0-4461-b8fe-6ff18a65c6cc resourceVersion: "51843" uid: 70d312b2-a66d-480a-b140-35814a9291e5 spec: sourcePod: network-check-source-6f78d59f99-5ks6c targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T18:07:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.145466ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:55:51Z" - latency: 2.041872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:55:51Z" - latency: 913.528µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:54:51Z" - latency: 2.304977ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:54:51Z" - latency: 922.987µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:53:51Z" - latency: 1.773077ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:53:51Z" - latency: 917.243µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:52:51Z" - latency: 1.993369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:52:51Z" - latency: 929.836µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:51:51Z" - latency: 1.931579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:51:51Z" kind: List metadata: resourceVersion: ""