apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:03:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.ec2.internal uid: f31698a0-cd10-4199-af3e-f4fd60f694c4 resourceVersion: "28806" uid: a2bc90c1-0f98-446a-9604-4f01c7bca474 spec: sourcePod: network-check-source-dbd9cf844-n62dt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T15:10:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.127977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:20Z" - latency: 1.093674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:20Z" - latency: 995.464µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:20Z" - latency: 1.123732ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:20Z" - latency: 918.079µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:13:20Z" - latency: 1.21388ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:12:20Z" - latency: 1.351561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:11:20Z" - latency: 1.763114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:10:20Z" - latency: 1.143346ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:09:20Z" - latency: 871.387µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:08:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:03:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.ec2.internal uid: f31698a0-cd10-4199-af3e-f4fd60f694c4 resourceVersion: "31217" uid: 23febc11-88cc-4785-903f-ce8b337336e7 spec: sourcePod: network-check-source-dbd9cf844-n62dt targetEndpoint: a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:09:20Z" message: 'load-balancer-api-external: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.650384ms message: 'load-balancer-api-external: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:20Z" - latency: 14.504076ms message: 'load-balancer-api-external: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:21:20Z" - latency: 4.67549ms message: 'load-balancer-api-external: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:20:20Z" - latency: 11.439306ms message: 'load-balancer-api-external: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:20:20Z" - latency: 3.970822ms message: 'load-balancer-api-external: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:19:20Z" - latency: 9.527011ms message: 'load-balancer-api-external: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:19:20Z" - latency: 5.383113ms message: 'load-balancer-api-external: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:20Z" - latency: 9.126894ms message: 'load-balancer-api-external: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:18:20Z" - latency: 5.34128ms message: 'load-balancer-api-external: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:20Z" - latency: 9.782103ms message: 'load-balancer-api-external: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:17:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:03:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.ec2.internal uid: f31698a0-cd10-4199-af3e-f4fd60f694c4 resourceVersion: "31216" uid: 59ce935c-6752-4a20-bc8e-7fb368a7b103 spec: sourcePod: network-check-source-dbd9cf844-n62dt targetEndpoint: a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:09:20Z" message: 'load-balancer-api-internal: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.34648ms message: 'load-balancer-api-internal: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:20Z" - latency: 14.423673ms message: 'load-balancer-api-internal: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:21:20Z" - latency: 4.732936ms message: 'load-balancer-api-internal: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:20:20Z" - latency: 11.453724ms message: 'load-balancer-api-internal: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:20:20Z" - latency: 3.975458ms message: 'load-balancer-api-internal: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:19:20Z" - latency: 9.486871ms message: 'load-balancer-api-internal: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:19:20Z" - latency: 5.551614ms message: 'load-balancer-api-internal: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:20Z" - latency: 9.047761ms message: 'load-balancer-api-internal: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:18:20Z" - latency: 6.056663ms message: 'load-balancer-api-internal: tcp connection to a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:20Z" - latency: 9.696421ms message: 'load-balancer-api-internal: resolved host name a308cd6963a30400ab5e76b26d49a4f6-eb6b7bcb4cdbea9a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:17:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:03:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-network-check-target-ip-10-0-128-43 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.ec2.internal uid: f31698a0-cd10-4199-af3e-f4fd60f694c4 resourceVersion: "28803" uid: 21529f12-bf6c-454a-92fc-db9c8152bf3a spec: sourcePod: network-check-source-dbd9cf844-n62dt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:10:20Z" message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.137µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:20Z" - latency: 890.808µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:20Z" - latency: 936.857µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:20Z" - latency: 910.263µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:20Z" - latency: 1.450961ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:13:20Z" - latency: 848.533µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:12:20Z" - latency: 1.319883ms message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:11:20Z" - latency: 807.173µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:10:20Z" - latency: 912.367µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:09:20Z" - latency: 967.306µs message: 'network-check-target-ip-10-0-128-43: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:08:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:03:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-network-check-target-ip-10-0-134-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.ec2.internal uid: f31698a0-cd10-4199-af3e-f4fd60f694c4 resourceVersion: "28804" uid: 7a4a82d4-2387-4742-96da-cf7855d837e2 spec: sourcePod: network-check-source-dbd9cf844-n62dt targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:10:20Z" message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.934458ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:20Z" - latency: 2.232835ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:20Z" - latency: 2.233108ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:20Z" - latency: 2.461572ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:20Z" - latency: 2.127991ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:13:20Z" - latency: 2.208528ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:12:20Z" - latency: 2.755467ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:11:20Z" - latency: 2.194915ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:10:20Z" - latency: 2.590799ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:09:20Z" - latency: 2.65322ms message: 'network-check-target-ip-10-0-134-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:08:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:03:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-network-check-target-ip-10-0-140-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.ec2.internal uid: f31698a0-cd10-4199-af3e-f4fd60f694c4 resourceVersion: "28805" uid: 2f8dee8d-4476-42bd-b7b6-ff81f6b85d11 spec: sourcePod: network-check-source-dbd9cf844-n62dt targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:10:20Z" message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.50818ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:20Z" - latency: 2.210392ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:16:20Z" - latency: 2.407003ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:15:20Z" - latency: 2.406721ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:14:20Z" - latency: 2.266577ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:13:20Z" - latency: 2.479771ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:12:20Z" - latency: 2.2088ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:11:20Z" - latency: 2.793629ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:10:20Z" - latency: 2.19391ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:09:20Z" - latency: 2.164072ms message: 'network-check-target-ip-10-0-140-77: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:08:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:03:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-43-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-43.ec2.internal uid: f31698a0-cd10-4199-af3e-f4fd60f694c4 resourceVersion: "31214" uid: ebb45d6a-68d7-4707-be73-230e69b3bd22 spec: sourcePod: network-check-source-dbd9cf844-n62dt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T15:09:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.016812ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:20Z" - latency: 1.907435ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:21:20Z" - latency: 750.612µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:20:20Z" - latency: 1.642684ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:20:20Z" - latency: 888.14µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:19:20Z" - latency: 1.584382ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:19:20Z" - latency: 805.859µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:18:20Z" - latency: 1.690212ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:18:20Z" - latency: 912.885µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:17:20Z" - latency: 1.785185ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:17:20Z" kind: List metadata: resourceVersion: ""