apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T22:08:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-202-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-202.ec2.internal uid: d39f80ab-47c3-4856-a97a-1c034fdbd7c9 resourceVersion: "26705" uid: 983a586c-82ce-4e2a-b8c8-1ca666bac96d spec: sourcePod: network-check-source-989f8b8dc-m6tzs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T22:15:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.099817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:22:49Z" - latency: 1.234641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:21:49Z" - latency: 1.476431ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:20:49Z" - latency: 1.430199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:19:49Z" - latency: 1.624271ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:18:49Z" - latency: 1.04804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:17:49Z" - latency: 1.321987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:16:49Z" - latency: 1.212522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:15:49Z" - latency: 1.306475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:14:49Z" - latency: 989.61µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:13:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T22:08:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-202-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-202.ec2.internal uid: d39f80ab-47c3-4856-a97a-1c034fdbd7c9 resourceVersion: "25504" uid: aed99238-4637-463a-94e8-1ef80f0d8a3d spec: sourcePod: network-check-source-989f8b8dc-m6tzs targetEndpoint: a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T22:14:49Z" message: 'load-balancer-api-external: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.197697ms message: 'load-balancer-api-external: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:20:49Z" - latency: 8.590948ms message: 'load-balancer-api-external: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:20:49Z" - latency: 4.611352ms message: 'load-balancer-api-external: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:19:49Z" - latency: 9.174245ms message: 'load-balancer-api-external: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:19:49Z" - latency: 4.312716ms message: 'load-balancer-api-external: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:18:49Z" - latency: 9.020515ms message: 'load-balancer-api-external: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:18:49Z" - latency: 4.972604ms message: 'load-balancer-api-external: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:17:49Z" - latency: 9.018958ms message: 'load-balancer-api-external: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:17:49Z" - latency: 5.245351ms message: 'load-balancer-api-external: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:16:49Z" - latency: 8.500066ms message: 'load-balancer-api-external: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:16:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T22:08:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-202-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-202.ec2.internal uid: d39f80ab-47c3-4856-a97a-1c034fdbd7c9 resourceVersion: "25503" uid: fc831e4f-cf32-4ba5-a38f-c384178e89c7 spec: sourcePod: network-check-source-989f8b8dc-m6tzs targetEndpoint: a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T22:14:49Z" message: 'load-balancer-api-internal: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.426887ms message: 'load-balancer-api-internal: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:20:49Z" - latency: 8.612111ms message: 'load-balancer-api-internal: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:20:49Z" - latency: 4.669923ms message: 'load-balancer-api-internal: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:19:49Z" - latency: 9.227992ms message: 'load-balancer-api-internal: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:19:49Z" - latency: 5.099456ms message: 'load-balancer-api-internal: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:18:49Z" - latency: 9.056676ms message: 'load-balancer-api-internal: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:18:49Z" - latency: 4.961609ms message: 'load-balancer-api-internal: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:17:49Z" - latency: 9.069786ms message: 'load-balancer-api-internal: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:17:49Z" - latency: 5.294622ms message: 'load-balancer-api-internal: tcp connection to a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:16:49Z" - latency: 8.583148ms message: 'load-balancer-api-internal: resolved host name a2f84e81403784632a79b2f5edf5ca2e-60f4c9c0fefc52fd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T22:16:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T22:08:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-202-to-network-check-target-ip-10-0-128-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-202.ec2.internal uid: d39f80ab-47c3-4856-a97a-1c034fdbd7c9 resourceVersion: "26702" uid: 7b84bb1b-f6f9-4f04-85a7-57241bafe74d spec: sourcePod: network-check-source-989f8b8dc-m6tzs targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T22:15:49Z" message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.461287ms message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:22:49Z" - latency: 1.025833ms message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:21:49Z" - latency: 1.069198ms message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:20:49Z" - latency: 1.044351ms message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:19:49Z" - latency: 989.487µs message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:18:49Z" - latency: 1.184677ms message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:17:49Z" - latency: 974.375µs message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:16:49Z" - latency: 1.886022ms message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:15:49Z" - latency: 959.638µs message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:14:49Z" - latency: 1.029639ms message: 'network-check-target-ip-10-0-128-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:13:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T22:08:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-202-to-network-check-target-ip-10-0-133-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-202.ec2.internal uid: d39f80ab-47c3-4856-a97a-1c034fdbd7c9 resourceVersion: "26703" uid: 8908efac-231f-496d-98cf-1855c832a29e spec: sourcePod: network-check-source-989f8b8dc-m6tzs targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-02T22:15:49Z" message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.215437ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:22:49Z" - latency: 2.184875ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:21:49Z" - latency: 2.119752ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:20:49Z" - latency: 2.343778ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:19:49Z" - latency: 2.268731ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:18:49Z" - latency: 1.954351ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:17:49Z" - latency: 2.263034ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:16:49Z" - latency: 2.203534ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:15:49Z" - latency: 2.142279ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:14:49Z" - latency: 2.057281ms message: 'network-check-target-ip-10-0-133-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:13:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T22:08:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-202-to-network-check-target-ip-10-0-133-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-202.ec2.internal uid: d39f80ab-47c3-4856-a97a-1c034fdbd7c9 resourceVersion: "26704" uid: 17d88b03-3817-4dfa-a426-519cfe10fd67 spec: sourcePod: network-check-source-989f8b8dc-m6tzs targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T22:15:49Z" message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.286234ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:22:49Z" - latency: 2.045034ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:21:49Z" - latency: 1.982982ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:20:49Z" - latency: 1.905346ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:19:49Z" - latency: 1.769196ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:18:49Z" - latency: 1.967746ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:17:49Z" - latency: 2.001632ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:16:49Z" - latency: 2.223939ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:15:49Z" - latency: 2.288726ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:14:49Z" - latency: 3.202034ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:13:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T22:08:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-202-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-202.ec2.internal uid: d39f80ab-47c3-4856-a97a-1c034fdbd7c9 resourceVersion: "25502" uid: e615c477-c6ea-4e1b-9137-073887274c24 spec: sourcePod: network-check-source-989f8b8dc-m6tzs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T22:14:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.386µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:20:49Z" - latency: 1.847006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T22:20:49Z" - latency: 1.142049ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:19:49Z" - latency: 1.730358ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T22:19:49Z" - latency: 1.072342ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:18:49Z" - latency: 1.914796ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T22:18:49Z" - latency: 866.482µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:17:49Z" - latency: 1.946448ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T22:17:49Z" - latency: 1.05152ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T22:16:49Z" - latency: 1.740778ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T22:16:49Z" kind: List metadata: resourceVersion: ""