apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.us-west-1.compute.internal uid: 54c620b7-4678-4af9-88f9-c6bb30f13b6d resourceVersion: "93051" uid: 98d3cadf-2375-4c22-8191-8800d509f3ee spec: sourcePod: network-check-source-6f78d59f99-7wr6f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:51:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.202744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:19Z" - latency: 937.438µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:19Z" - latency: 1.145912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:19Z" - latency: 1.630218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:19Z" - latency: 1.239943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:19Z" - latency: 1.343739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:19Z" - latency: 1.306523ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:19Z" - latency: 1.155607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:19Z" - latency: 1.281092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:19Z" - latency: 847.342µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.us-west-1.compute.internal uid: 54c620b7-4678-4af9-88f9-c6bb30f13b6d resourceVersion: "95717" uid: 3a238fe1-9cac-4c76-a4ad-a2596e8c8748 spec: sourcePod: network-check-source-6f78d59f99-7wr6f targetEndpoint: ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:50:19Z" message: 'load-balancer-api-external: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.964348ms message: 'load-balancer-api-external: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:19Z" - latency: 6.200954ms message: 'load-balancer-api-external: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:44:19Z" - latency: 52.708455ms message: 'load-balancer-api-external: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:19Z" - latency: 5.984552ms message: 'load-balancer-api-external: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:43:19Z" - latency: 52.70831ms message: 'load-balancer-api-external: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:19Z" - latency: 6.537377ms message: 'load-balancer-api-external: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:19Z" - latency: 56.438532ms message: 'load-balancer-api-external: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:19Z" - latency: 6.556682ms message: 'load-balancer-api-external: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:41:19Z" - latency: 54.803718ms message: 'load-balancer-api-external: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:19Z" - latency: 6.770266ms message: 'load-balancer-api-external: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.us-west-1.compute.internal uid: 54c620b7-4678-4af9-88f9-c6bb30f13b6d resourceVersion: "95718" uid: 5df3418f-985f-4a56-8f0e-6dcda932c328 spec: sourcePod: network-check-source-6f78d59f99-7wr6f targetEndpoint: ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:50:19Z" message: 'load-balancer-api-internal: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.956228ms message: 'load-balancer-api-internal: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:19Z" - latency: 6.290702ms message: 'load-balancer-api-internal: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:44:19Z" - latency: 52.705517ms message: 'load-balancer-api-internal: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:19Z" - latency: 6.039917ms message: 'load-balancer-api-internal: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:43:19Z" - latency: 54.198989ms message: 'load-balancer-api-internal: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:19Z" - latency: 6.593628ms message: 'load-balancer-api-internal: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:19Z" - latency: 54.497565ms message: 'load-balancer-api-internal: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:19Z" - latency: 6.598785ms message: 'load-balancer-api-internal: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:41:19Z" - latency: 54.313614ms message: 'load-balancer-api-internal: tcp connection to ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:19Z" - latency: 6.741868ms message: 'load-balancer-api-internal: resolved host name ad8669e46bc8f4e2bbe5ac45b704f8a7-5cb0796d801b0643.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:40:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-131-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.us-west-1.compute.internal uid: 54c620b7-4678-4af9-88f9-c6bb30f13b6d resourceVersion: "93046" uid: e8d74b2f-de52-4cf0-bef0-a3949e7fe31f spec: sourcePod: network-check-source-6f78d59f99-7wr6f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:19Z" message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 908.614µs message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:19Z" - latency: 1.094496ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:19Z" - latency: 931.283µs message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:19Z" - latency: 875.534µs message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:19Z" - latency: 999.18µs message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:19Z" - latency: 1.136844ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:19Z" - latency: 1.383334ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:19Z" - latency: 1.045617ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:19Z" - latency: 1.461809ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:19Z" - latency: 1.137312ms message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-134-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.us-west-1.compute.internal uid: 54c620b7-4678-4af9-88f9-c6bb30f13b6d resourceVersion: "93047" uid: 26834a9f-8dc5-426b-b20b-acfd374e5300 spec: sourcePod: network-check-source-6f78d59f99-7wr6f targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:19Z" message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.04761ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:19Z" - latency: 2.062517ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:19Z" - latency: 1.94802ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:19Z" - latency: 1.948302ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:19Z" - latency: 2.006502ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:19Z" - latency: 2.021357ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:19Z" - latency: 1.925736ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:19Z" - latency: 2.185813ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:19Z" - latency: 2.11023ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:19Z" - latency: 1.981924ms message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-network-check-target-ip-10-0-140-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.us-west-1.compute.internal uid: 54c620b7-4678-4af9-88f9-c6bb30f13b6d resourceVersion: "93049" uid: 375848bb-5665-419a-ae24-c13fc769a8d2 spec: sourcePod: network-check-source-6f78d59f99-7wr6f targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:19Z" message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.483181ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:19Z" - latency: 2.166763ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:39:19Z" - latency: 2.597237ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:38:19Z" - latency: 2.364018ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:37:19Z" - latency: 2.423668ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:19Z" - latency: 2.435765ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:19Z" - latency: 2.679965ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:19Z" - latency: 2.598284ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:19Z" - latency: 2.435899ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:19Z" - latency: 2.227458ms message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-250.us-west-1.compute.internal uid: 54c620b7-4678-4af9-88f9-c6bb30f13b6d resourceVersion: "95715" uid: 29f027a8-752f-40e0-95d7-f6c6b59b6262 spec: sourcePod: network-check-source-6f78d59f99-7wr6f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:50:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.516µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:19Z" - latency: 1.828346ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:44:19Z" - latency: 1.055099ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:19Z" - latency: 1.906639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:43:19Z" - latency: 1.079519ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:42:19Z" - latency: 1.905767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:42:19Z" - latency: 911.97µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:41:19Z" - latency: 1.801089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:41:19Z" - latency: 910.847µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:40:19Z" - latency: 2.139939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:40:19Z" kind: List metadata: resourceVersion: ""