apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:54:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.us-east-2.compute.internal uid: 7f5d37e4-e6da-4fd3-86ab-529b1f131bbf resourceVersion: "32749" uid: 45f7d951-abf3-4f36-8c19-62347db07278 spec: sourcePod: network-check-source-6f78d59f99-zhh2r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T22:01:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 766.58µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:04:51Z" - latency: 1.081681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:03:51Z" - latency: 817.937µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:51Z" - latency: 893.346µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:01:51Z" - latency: 1.065045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:00:51Z" - latency: 1.060551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:59:51Z" - latency: 1.003113ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:51Z" - latency: 1.223822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:51Z" - latency: 1.34871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:51Z" - latency: 1.004702ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:54:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.us-east-2.compute.internal uid: 7f5d37e4-e6da-4fd3-86ab-529b1f131bbf resourceVersion: "33208" uid: bf9231c9-e0b8-437c-932e-e3f843f043bb spec: sourcePod: network-check-source-6f78d59f99-zhh2r targetEndpoint: aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T22:00:51Z" message: 'load-balancer-api-external: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.878521ms message: 'load-balancer-api-external: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:06:51Z" - latency: 6.525274ms message: 'load-balancer-api-external: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:06:51Z" - latency: 5.250465ms message: 'load-balancer-api-external: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:05:51Z" - latency: 7.480528ms message: 'load-balancer-api-external: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:05:51Z" - latency: 5.470636ms message: 'load-balancer-api-external: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:04:51Z" - latency: 6.205137ms message: 'load-balancer-api-external: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:04:51Z" - latency: 5.673428ms message: 'load-balancer-api-external: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:03:51Z" - latency: 7.15617ms message: 'load-balancer-api-external: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:03:51Z" - latency: 5.407556ms message: 'load-balancer-api-external: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:51Z" - latency: 6.123102ms message: 'load-balancer-api-external: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:02:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:54:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.us-east-2.compute.internal uid: 7f5d37e4-e6da-4fd3-86ab-529b1f131bbf resourceVersion: "33207" uid: 014ac276-5eda-4992-9de5-f3c3372c8bc7 spec: sourcePod: network-check-source-6f78d59f99-zhh2r targetEndpoint: aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T22:00:51Z" message: 'load-balancer-api-internal: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.352502ms message: 'load-balancer-api-internal: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:06:51Z" - latency: 6.648131ms message: 'load-balancer-api-internal: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:06:51Z" - latency: 5.328674ms message: 'load-balancer-api-internal: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:05:51Z" - latency: 7.597313ms message: 'load-balancer-api-internal: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:05:51Z" - latency: 5.427107ms message: 'load-balancer-api-internal: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:04:51Z" - latency: 6.318704ms message: 'load-balancer-api-internal: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:04:51Z" - latency: 5.705029ms message: 'load-balancer-api-internal: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:03:51Z" - latency: 7.060258ms message: 'load-balancer-api-internal: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:03:51Z" - latency: 5.419321ms message: 'load-balancer-api-internal: tcp connection to aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:51Z" - latency: 6.196754ms message: 'load-balancer-api-internal: resolved host name aa48db78fc343447e9925217d1fb9efc-13fd6638800c364b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T23:02:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:54:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-130-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.us-east-2.compute.internal uid: 7f5d37e4-e6da-4fd3-86ab-529b1f131bbf resourceVersion: "32746" uid: 1bff25e0-b1b6-4517-a5a4-6b8997154c7a spec: sourcePod: network-check-source-6f78d59f99-zhh2r targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:01:51Z" message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 732.899µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:04:51Z" - latency: 831.354µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:03:51Z" - latency: 961.064µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:51Z" - latency: 755.913µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:01:51Z" - latency: 848.124µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:00:51Z" - latency: 1.2333ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:59:51Z" - latency: 1.000635ms message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:51Z" - latency: 736.917µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:51Z" - latency: 730.698µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:51Z" - latency: 651.028µs message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:54:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-131-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.us-east-2.compute.internal uid: 7f5d37e4-e6da-4fd3-86ab-529b1f131bbf resourceVersion: "32748" uid: 374de4e9-8b85-4df8-8635-dbf99d408e21 spec: sourcePod: network-check-source-6f78d59f99-zhh2r targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:01:51Z" message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.325507ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:04:51Z" - latency: 2.544478ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:03:51Z" - latency: 1.989818ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:51Z" - latency: 1.758266ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:01:51Z" - latency: 2.371862ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:00:51Z" - latency: 2.182284ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:59:51Z" - latency: 2.00614ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:51Z" - latency: 2.219283ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:51Z" - latency: 2.865919ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:51Z" - latency: 2.447828ms message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:54:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-network-check-target-ip-10-0-139-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.us-east-2.compute.internal uid: 7f5d37e4-e6da-4fd3-86ab-529b1f131bbf resourceVersion: "32747" uid: 686f2501-3ae2-4fde-b1b4-4a57d6017303 spec: sourcePod: network-check-source-6f78d59f99-zhh2r targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T22:01:51Z" message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.932038ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:04:51Z" - latency: 1.86403ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:03:51Z" - latency: 1.945617ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:51Z" - latency: 1.690828ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:01:51Z" - latency: 1.831635ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:00:51Z" - latency: 1.86376ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:59:51Z" - latency: 1.761955ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:58:51Z" - latency: 1.812737ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:57:51Z" - latency: 1.932505ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:56:51Z" - latency: 1.886647ms message: 'network-check-target-ip-10-0-139-99: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T22:55:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T21:54:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-133-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-133.us-east-2.compute.internal uid: 7f5d37e4-e6da-4fd3-86ab-529b1f131bbf resourceVersion: "33206" uid: 135e236c-1b61-4e9c-9667-f3d404844d2f spec: sourcePod: network-check-source-6f78d59f99-zhh2r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T22:00:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.683µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:06:51Z" - latency: 1.693559ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T23:06:51Z" - latency: 782.46µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:05:51Z" - latency: 1.71571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T23:05:51Z" - latency: 895.296µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:04:51Z" - latency: 1.510384ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T23:04:51Z" - latency: 1.204999ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:03:51Z" - latency: 1.687509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T23:03:51Z" - latency: 715.71µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T23:02:51Z" - latency: 1.964355ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T23:02:51Z" kind: List metadata: resourceVersion: ""