apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:54:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.us-west-2.compute.internal uid: bb020282-6964-4dd3-9434-1586ece4461f resourceVersion: "169606" uid: 0e4236d4-6889-4114-a837-03026c85b14d spec: sourcePod: network-check-source-6f78d59f99-6zkx2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T23:01:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.656306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:46:38Z" - latency: 1.21905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:38Z" - latency: 1.308715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:38Z" - latency: 1.197035ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:38Z" - latency: 960.344µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:38Z" - latency: 1.136604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:38Z" - latency: 1.52604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:40:38Z" - latency: 1.263867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:39:38Z" - latency: 1.170269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:38:38Z" - latency: 1.116223ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:37:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:54:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.us-west-2.compute.internal uid: bb020282-6964-4dd3-9434-1586ece4461f resourceVersion: "171070" uid: 30fa4845-d356-46e4-8181-7033d207570c spec: sourcePod: network-check-source-6f78d59f99-6zkx2 targetEndpoint: a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T23:00:38Z" message: 'load-balancer-api-external: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.058437ms message: 'load-balancer-api-external: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:48:38Z" - latency: 8.294719ms message: 'load-balancer-api-external: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:48:38Z" - latency: 50.220333ms message: 'load-balancer-api-external: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:47:38Z" - latency: 7.671564ms message: 'load-balancer-api-external: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:47:38Z" - latency: 50.477349ms message: 'load-balancer-api-external: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:46:38Z" - latency: 7.567605ms message: 'load-balancer-api-external: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:46:38Z" - latency: 56.411882ms message: 'load-balancer-api-external: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:38Z" - latency: 8.057392ms message: 'load-balancer-api-external: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:45:38Z" - latency: 51.84781ms message: 'load-balancer-api-external: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:38Z" - latency: 8.572901ms message: 'load-balancer-api-external: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:44:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:54:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.us-west-2.compute.internal uid: bb020282-6964-4dd3-9434-1586ece4461f resourceVersion: "171067" uid: a4d6e9dd-331d-452c-8d3c-6abb67629959 spec: sourcePod: network-check-source-6f78d59f99-6zkx2 targetEndpoint: a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T23:00:38Z" message: 'load-balancer-api-internal: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.852221ms message: 'load-balancer-api-internal: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:48:38Z" - latency: 8.333881ms message: 'load-balancer-api-internal: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:48:38Z" - latency: 50.240484ms message: 'load-balancer-api-internal: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:47:38Z" - latency: 7.611869ms message: 'load-balancer-api-internal: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:47:38Z" - latency: 50.489754ms message: 'load-balancer-api-internal: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:46:38Z" - latency: 7.514405ms message: 'load-balancer-api-internal: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:46:38Z" - latency: 56.411952ms message: 'load-balancer-api-internal: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:38Z" - latency: 7.953149ms message: 'load-balancer-api-internal: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:45:38Z" - latency: 56.050348ms message: 'load-balancer-api-internal: tcp connection to a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:38Z" - latency: 8.590765ms message: 'load-balancer-api-internal: resolved host name a2b73d5d16d574ed99182329d58f278a-a10e0d37d7b270df.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T00:44:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:54:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-network-check-target-ip-10-0-130-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.us-west-2.compute.internal uid: bb020282-6964-4dd3-9434-1586ece4461f resourceVersion: "169601" uid: cd64686a-a216-41cb-abda-1c95ab3b1136 spec: sourcePod: network-check-source-6f78d59f99-6zkx2 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T23:01:38Z" message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 960.261µs message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:46:38Z" - latency: 1.497095ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:38Z" - latency: 1.58175ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:38Z" - latency: 1.269832ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:38Z" - latency: 1.387762ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:38Z" - latency: 784.032µs message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:38Z" - latency: 1.111755ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:40:38Z" - latency: 936.94µs message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:39:38Z" - latency: 1.019837ms message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:38:38Z" - latency: 928.296µs message: 'network-check-target-ip-10-0-130-211: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:37:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:54:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-network-check-target-ip-10-0-137-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.us-west-2.compute.internal uid: bb020282-6964-4dd3-9434-1586ece4461f resourceVersion: "169602" uid: 1be314f8-2b03-42f2-a5fd-661ace07b810 spec: sourcePod: network-check-source-6f78d59f99-6zkx2 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T23:01:38Z" message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.811015ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:46:38Z" - latency: 1.768347ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:38Z" - latency: 1.747499ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:38Z" - latency: 2.003174ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:38Z" - latency: 2.103409ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:38Z" - latency: 1.905992ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:38Z" - latency: 1.84604ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:40:38Z" - latency: 1.929156ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:39:38Z" - latency: 1.793761ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:38:38Z" - latency: 1.95468ms message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:37:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:54:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-network-check-target-ip-10-0-139-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.us-west-2.compute.internal uid: bb020282-6964-4dd3-9434-1586ece4461f resourceVersion: "169603" uid: fe719858-61aa-41b4-9154-7ef3d8b4a8b9 spec: sourcePod: network-check-source-6f78d59f99-6zkx2 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T23:01:38Z" message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.409836ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:46:38Z" - latency: 2.565565ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:38Z" - latency: 2.349988ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:38Z" - latency: 2.58888ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:43:38Z" - latency: 2.647334ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:42:38Z" - latency: 2.274449ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:41:38Z" - latency: 2.362215ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:40:38Z" - latency: 2.492683ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:39:38Z" - latency: 2.620871ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:38:38Z" - latency: 2.484839ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:37:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T22:54:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-211-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-211.us-west-2.compute.internal uid: bb020282-6964-4dd3-9434-1586ece4461f resourceVersion: "171068" uid: 91acb7ec-6741-4856-86b0-e9dcd7aeb386 spec: sourcePod: network-check-source-6f78d59f99-6zkx2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T23:00:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.096879ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:48:38Z" - latency: 818.403µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:48:38Z" - latency: 1.415432ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:47:38Z" - latency: 614.2µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:47:38Z" - latency: 1.236192ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:46:38Z" - latency: 618.285µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:46:38Z" - latency: 1.491785ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:45:38Z" - latency: 699.664µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:45:38Z" - latency: 1.161115ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T00:44:38Z" - latency: 753.017µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T00:44:38Z" kind: List metadata: resourceVersion: ""