apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 621f9aca-c031-4f2f-a198-10592fb3378e resourceVersion: "20875" uid: b798a0d3-e271-4258-b80f-9627372431d7 spec: sourcePod: network-check-source-6f78d59f99-v5ppj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T03:04:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.019157ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:25:18Z" - latency: 742.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:24:18Z" - latency: 977.573µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:23:18Z" - latency: 817.284µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:22:18Z" - latency: 1.388314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:21:18Z" - latency: 916.035µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:20:18Z" - latency: 1.004894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:19:18Z" - latency: 990.985µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:18:18Z" - latency: 1.063257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:17:18Z" - latency: 1.0655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:16:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 621f9aca-c031-4f2f-a198-10592fb3378e resourceVersion: "21826" uid: 38cc9cbb-9339-4bc8-bf83-b1acba24d21c spec: sourcePod: network-check-source-6f78d59f99-v5ppj targetEndpoint: a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T03:03:18Z" message: 'load-balancer-api-external: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.348193808s message: 'load-balancer-api-external: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:27:18Z" - latency: 7.758845ms message: 'load-balancer-api-external: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:27:18Z" - latency: 14.981563ms message: 'load-balancer-api-external: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:26:18Z" - latency: 6.716591ms message: 'load-balancer-api-external: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:26:18Z" - latency: 17.268471ms message: 'load-balancer-api-external: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:25:18Z" - latency: 7.383008ms message: 'load-balancer-api-external: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:25:18Z" - latency: 16.865232ms message: 'load-balancer-api-external: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:24:18Z" - latency: 9.056682ms message: 'load-balancer-api-external: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:24:18Z" - latency: 17.679812ms message: 'load-balancer-api-external: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:23:18Z" - latency: 6.919712ms message: 'load-balancer-api-external: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:23:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 621f9aca-c031-4f2f-a198-10592fb3378e resourceVersion: "21812" uid: 107880c3-23db-401e-b9de-06421feddd98 spec: sourcePod: network-check-source-6f78d59f99-v5ppj targetEndpoint: a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T03:03:18Z" message: 'load-balancer-api-internal: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.756445ms message: 'load-balancer-api-internal: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:27:18Z" - latency: 7.715037ms message: 'load-balancer-api-internal: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:27:18Z" - latency: 16.725523ms message: 'load-balancer-api-internal: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:26:18Z" - latency: 6.746382ms message: 'load-balancer-api-internal: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:26:18Z" - latency: 16.407668ms message: 'load-balancer-api-internal: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:25:18Z" - latency: 7.317265ms message: 'load-balancer-api-internal: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:25:18Z" - latency: 18.050669ms message: 'load-balancer-api-internal: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:24:18Z" - latency: 9.105656ms message: 'load-balancer-api-internal: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:24:18Z" - latency: 15.742293ms message: 'load-balancer-api-internal: tcp connection to a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:23:18Z" - latency: 6.864082ms message: 'load-balancer-api-internal: resolved host name a234876b2a0974e47b2c240e6598901d-dc7adf45297ea227.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T03:23:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-network-check-target-ip-10-0-139-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 621f9aca-c031-4f2f-a198-10592fb3378e resourceVersion: "20872" uid: ee3b1c45-2b3a-4ac8-b67f-59d3ffd05563 spec: sourcePod: network-check-source-6f78d59f99-v5ppj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T03:04:18Z" message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.104µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:25:18Z" - latency: 870.835µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:24:18Z" - latency: 912.059µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:23:18Z" - latency: 943.587µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:22:18Z" - latency: 1.265024ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:21:18Z" - latency: 1.003185ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:20:18Z" - latency: 1.530104ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:19:18Z" - latency: 941.656µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:18:18Z" - latency: 1.028119ms message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:17:18Z" - latency: 825.46µs message: 'network-check-target-ip-10-0-139-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:16:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-network-check-target-ip-10-0-140-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 621f9aca-c031-4f2f-a198-10592fb3378e resourceVersion: "20874" uid: 69004dc0-772e-4ef5-8bc4-eac72b493e67 spec: sourcePod: network-check-source-6f78d59f99-v5ppj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T03:04:18Z" message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186544ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:25:18Z" - latency: 2.23061ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:24:18Z" - latency: 2.364559ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:23:18Z" - latency: 2.09839ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:22:18Z" - latency: 2.245675ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:21:18Z" - latency: 2.252553ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:20:18Z" - latency: 2.076261ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:19:18Z" - latency: 2.288786ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:18:18Z" - latency: 2.240539ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:17:18Z" - latency: 1.970517ms message: 'network-check-target-ip-10-0-140-17: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:16:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-network-check-target-ip-10-0-142-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 621f9aca-c031-4f2f-a198-10592fb3378e resourceVersion: "20871" uid: 49f87b89-7a2c-4a94-b812-eec9bf7e9abb spec: sourcePod: network-check-source-6f78d59f99-v5ppj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T03:04:18Z" message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.990008ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:25:18Z" - latency: 1.762045ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:24:18Z" - latency: 1.917636ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:23:18Z" - latency: 2.012445ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:22:18Z" - latency: 1.789658ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:21:18Z" - latency: 1.931828ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:20:18Z" - latency: 1.786883ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:19:18Z" - latency: 1.937772ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:18:18Z" - latency: 1.770826ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:17:18Z" - latency: 1.947706ms message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:16:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-40-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-40.ec2.internal uid: 621f9aca-c031-4f2f-a198-10592fb3378e resourceVersion: "21810" uid: 3aa97eb5-b118-4b2b-aad4-0d4cbd909d9c spec: sourcePod: network-check-source-6f78d59f99-v5ppj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T03:03:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:27:18Z" - latency: 2.248221ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T03:27:18Z" - latency: 969.156µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:26:18Z" - latency: 1.757251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T03:26:18Z" - latency: 1.077704ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:25:18Z" - latency: 1.884544ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T03:25:18Z" - latency: 1.126772ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:24:18Z" - latency: 1.635609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T03:24:18Z" - latency: 854.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T03:23:18Z" - latency: 1.794455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T03:23:18Z" kind: List metadata: resourceVersion: ""