apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T07:30:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-121-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-121.us-east-2.compute.internal uid: a7a371e2-e400-4bf9-8472-2d200ee333a0 resourceVersion: "33917" uid: c383c87e-39a1-4e6d-af8f-b9703827a696 spec: sourcePod: network-check-source-6f78d59f99-9sbwg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T07:37:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.14343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:26:42Z" - latency: 1.314518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:25:42Z" - latency: 2.125001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:24:42Z" - latency: 1.133608ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:23:42Z" - latency: 1.01309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:22:42Z" - latency: 1.286845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:21:42Z" - latency: 911.212µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:20:42Z" - latency: 912.617µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:19:42Z" - latency: 1.141336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:18:42Z" - latency: 1.296211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:17:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T07:30:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-121-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-121.us-east-2.compute.internal uid: a7a371e2-e400-4bf9-8472-2d200ee333a0 resourceVersion: "33154" uid: 5f3191be-ff44-46f7-be1f-3407eed3ebbc spec: sourcePod: network-check-source-6f78d59f99-9sbwg targetEndpoint: a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T07:36:42Z" message: 'load-balancer-api-external: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.476701ms message: 'load-balancer-api-external: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:24:42Z" - latency: 9.884862ms message: 'load-balancer-api-external: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:24:42Z" - latency: 6.138677ms message: 'load-balancer-api-external: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:23:42Z" - latency: 6.66947ms message: 'load-balancer-api-external: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:23:42Z" - latency: 5.470835ms message: 'load-balancer-api-external: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:22:42Z" - latency: 8.787897ms message: 'load-balancer-api-external: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:22:42Z" - latency: 5.230487ms message: 'load-balancer-api-external: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:21:42Z" - latency: 8.539533ms message: 'load-balancer-api-external: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:21:42Z" - latency: 5.73828ms message: 'load-balancer-api-external: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:20:42Z" - latency: 8.119238ms message: 'load-balancer-api-external: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:20:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T07:30:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-121-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-121.us-east-2.compute.internal uid: a7a371e2-e400-4bf9-8472-2d200ee333a0 resourceVersion: "33155" uid: f9748dd6-6dbc-4cc3-958b-478ab6c34b7d spec: sourcePod: network-check-source-6f78d59f99-9sbwg targetEndpoint: a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T07:36:42Z" message: 'load-balancer-api-internal: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.554364ms message: 'load-balancer-api-internal: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:24:42Z" - latency: 9.827625ms message: 'load-balancer-api-internal: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:24:42Z" - latency: 6.155625ms message: 'load-balancer-api-internal: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:23:42Z" - latency: 6.625733ms message: 'load-balancer-api-internal: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:23:42Z" - latency: 5.676735ms message: 'load-balancer-api-internal: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:22:42Z" - latency: 8.701148ms message: 'load-balancer-api-internal: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:22:42Z" - latency: 4.831176ms message: 'load-balancer-api-internal: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:21:42Z" - latency: 8.473736ms message: 'load-balancer-api-internal: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:21:42Z" - latency: 6.290685ms message: 'load-balancer-api-internal: tcp connection to a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:20:42Z" - latency: 8.034273ms message: 'load-balancer-api-internal: resolved host name a4eb3745dc5ca4341a2359bafca175c0-c5db754bacfef6eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T08:20:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T07:30:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-121-to-network-check-target-ip-10-0-128-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-121.us-east-2.compute.internal uid: a7a371e2-e400-4bf9-8472-2d200ee333a0 resourceVersion: "33916" uid: 13861989-eeec-47f8-bf7c-b103b8dfdf50 spec: sourcePod: network-check-source-6f78d59f99-9sbwg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T07:37:42Z" message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.201255ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:26:42Z" - latency: 2.088229ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:25:42Z" - latency: 2.601335ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:24:42Z" - latency: 2.22001ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:23:42Z" - latency: 2.34768ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:22:42Z" - latency: 2.43476ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:21:42Z" - latency: 2.017462ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:20:42Z" - latency: 2.209563ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:19:42Z" - latency: 2.256153ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:18:42Z" - latency: 2.528979ms message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:17:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T07:30:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-121-to-network-check-target-ip-10-0-130-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-121.us-east-2.compute.internal uid: a7a371e2-e400-4bf9-8472-2d200ee333a0 resourceVersion: "33914" uid: 6247110b-e897-4b68-9b98-eef3e29059b6 spec: sourcePod: network-check-source-6f78d59f99-9sbwg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T07:37:42Z" message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.914µs message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:26:42Z" - latency: 970.927µs message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:25:42Z" - latency: 878.347µs message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:24:42Z" - latency: 1.13958ms message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:23:42Z" - latency: 1.281155ms message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:22:42Z" - latency: 829.487µs message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:21:42Z" - latency: 788.85µs message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:20:42Z" - latency: 745.371µs message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:19:42Z" - latency: 1.010477ms message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:18:42Z" - latency: 869.934µs message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:17:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T07:30:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-121-to-network-check-target-ip-10-0-137-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-121.us-east-2.compute.internal uid: a7a371e2-e400-4bf9-8472-2d200ee333a0 resourceVersion: "33915" uid: cf607171-33f2-4e54-bf3f-7cfb1048a5f3 spec: sourcePod: network-check-source-6f78d59f99-9sbwg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T07:37:42Z" message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.759078ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:26:42Z" - latency: 2.03955ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:25:42Z" - latency: 2.537199ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:24:42Z" - latency: 1.885098ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:23:42Z" - latency: 2.119258ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:22:42Z" - latency: 2.045186ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:21:42Z" - latency: 2.066528ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:20:42Z" - latency: 1.842019ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:19:42Z" - latency: 1.922777ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:18:42Z" - latency: 1.9834ms message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:17:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T07:30:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-121-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-121.us-east-2.compute.internal uid: a7a371e2-e400-4bf9-8472-2d200ee333a0 resourceVersion: "33153" uid: 39f26cc2-a703-499e-a289-5a8f3edc9fcb spec: sourcePod: network-check-source-6f78d59f99-9sbwg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T07:36:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.875386ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:24:42Z" - latency: 1.815025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T08:24:42Z" - latency: 1.070317ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:23:42Z" - latency: 1.866814ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T08:23:42Z" - latency: 887.449µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:22:42Z" - latency: 1.990747ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T08:22:42Z" - latency: 908.14µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:21:42Z" - latency: 1.801423ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T08:21:42Z" - latency: 879.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T08:20:42Z" - latency: 2.063518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T08:20:42Z" kind: List metadata: resourceVersion: ""