apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:07:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-63.us-west-1.compute.internal uid: cae206de-1195-4f26-ac9b-d883dbc68b67 resourceVersion: "31966" uid: fd442e62-c9eb-4e3f-bd56-662971d8397d spec: sourcePod: network-check-source-6f78d59f99-62blg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T02:14:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.312205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:21:39Z" - latency: 1.660637ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:20:39Z" - latency: 1.065585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:19:39Z" - latency: 1.99641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:18:39Z" - latency: 861.704µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:17:39Z" - latency: 1.512201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:16:39Z" - latency: 765.454µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:15:39Z" - latency: 1.202217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:14:39Z" - latency: 1.48994ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:13:39Z" - latency: 1.050248ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:12:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:07:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-63.us-west-1.compute.internal uid: cae206de-1195-4f26-ac9b-d883dbc68b67 resourceVersion: "39583" uid: 8bfdc510-6f8d-4c0b-a065-b752cf662224 spec: sourcePod: network-check-source-6f78d59f99-62blg targetEndpoint: ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:13:39Z" message: 'load-balancer-api-external: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.478306ms message: 'load-balancer-api-external: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:25:39Z" - latency: 6.138402ms message: 'load-balancer-api-external: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:25:39Z" - latency: 52.583929ms message: 'load-balancer-api-external: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:24:39Z" - latency: 6.552218ms message: 'load-balancer-api-external: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:24:39Z" - latency: 53.320859ms message: 'load-balancer-api-external: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:23:39Z" - latency: 6.233815ms message: 'load-balancer-api-external: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:23:39Z" - latency: 54.820201ms message: 'load-balancer-api-external: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:22:39Z" - latency: 6.044077ms message: 'load-balancer-api-external: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:22:39Z" - latency: 55.116584ms message: 'load-balancer-api-external: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:21:39Z" - latency: 6.845102ms message: 'load-balancer-api-external: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:21:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:07:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-63.us-west-1.compute.internal uid: cae206de-1195-4f26-ac9b-d883dbc68b67 resourceVersion: "39584" uid: 50773f26-6925-48f9-a17f-4faefc195f70 spec: sourcePod: network-check-source-6f78d59f99-62blg targetEndpoint: ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:13:39Z" message: 'load-balancer-api-internal: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.46632ms message: 'load-balancer-api-internal: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:25:39Z" - latency: 6.078381ms message: 'load-balancer-api-internal: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:25:39Z" - latency: 52.742931ms message: 'load-balancer-api-internal: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:24:39Z" - latency: 6.513289ms message: 'load-balancer-api-internal: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:24:39Z" - latency: 52.700785ms message: 'load-balancer-api-internal: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:23:39Z" - latency: 6.266226ms message: 'load-balancer-api-internal: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:23:39Z" - latency: 55.533049ms message: 'load-balancer-api-internal: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:22:39Z" - latency: 6.009499ms message: 'load-balancer-api-internal: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:22:39Z" - latency: 55.013588ms message: 'load-balancer-api-internal: tcp connection to ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:21:39Z" - latency: 6.86976ms message: 'load-balancer-api-internal: resolved host name ac66bc7e1762247a7b68d1e1f0c05235-88944398bf9cb6fa.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:21:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:08:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-63-to-network-check-target-ip-10-0-135-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-63.us-west-1.compute.internal uid: cae206de-1195-4f26-ac9b-d883dbc68b67 resourceVersion: "32933" uid: 4f35308c-d4af-408a-90cd-5f7bc67bb100 spec: sourcePod: network-check-source-6f78d59f99-62blg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:15:03Z" message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.373556ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:22:03Z" - latency: 2.896428ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:21:03Z" - latency: 2.670582ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:20:03Z" - latency: 3.026736ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:19:03Z" - latency: 2.670267ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:18:03Z" - latency: 2.623275ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:17:03Z" - latency: 2.287589ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:16:03Z" - latency: 2.539505ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:15:03Z" - latency: 2.453569ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:14:03Z" - latency: 1.9565ms message: 'network-check-target-ip-10-0-135-225: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:13:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:07:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-63-to-network-check-target-ip-10-0-136-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-63.us-west-1.compute.internal uid: cae206de-1195-4f26-ac9b-d883dbc68b67 resourceVersion: "31964" uid: 76f7cac9-a96a-4be8-a131-46d8e23f8d71 spec: sourcePod: network-check-source-6f78d59f99-62blg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:14:39Z" message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 918.785µs message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:21:39Z" - latency: 912.443µs message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:20:39Z" - latency: 1.379754ms message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:19:39Z" - latency: 1.307868ms message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:18:39Z" - latency: 925.852µs message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:17:39Z" - latency: 852.349µs message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:16:39Z" - latency: 1.012371ms message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:15:39Z" - latency: 857.705µs message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:14:39Z" - latency: 1.622975ms message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:13:39Z" - latency: 1.377531ms message: 'network-check-target-ip-10-0-136-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:12:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:07:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-63-to-network-check-target-ip-10-0-138-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-63.us-west-1.compute.internal uid: cae206de-1195-4f26-ac9b-d883dbc68b67 resourceVersion: "31965" uid: 82612ae1-135a-4888-9b18-3308cecd2574 spec: sourcePod: network-check-source-6f78d59f99-62blg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:14:39Z" message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.534972ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:21:39Z" - latency: 2.451202ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:20:39Z" - latency: 2.698752ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:19:39Z" - latency: 2.722281ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:18:39Z" - latency: 2.162065ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:17:39Z" - latency: 12.500014ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:16:39Z" - latency: 2.200929ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:15:39Z" - latency: 1.596124ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:14:39Z" - latency: 1.829286ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:13:39Z" - latency: 1.91356ms message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:12:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:07:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-63.us-west-1.compute.internal uid: cae206de-1195-4f26-ac9b-d883dbc68b67 resourceVersion: "39580" uid: d82d9bcd-9c40-4fd9-bb75-d1fb4ac7cc2d spec: sourcePod: network-check-source-6f78d59f99-62blg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T02:13:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 975.734µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:25:39Z" - latency: 1.812252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:25:39Z" - latency: 1.920997ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:24:39Z" - latency: 2.254378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:24:39Z" - latency: 1.007111ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:23:39Z" - latency: 1.789311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:23:39Z" - latency: 991.759µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:22:39Z" - latency: 1.820486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:22:39Z" - latency: 1.368623ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:21:39Z" - latency: 2.103523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:21:39Z" kind: List metadata: resourceVersion: ""