Latest VKr versions compatible with the installed VKS service are not displayed.
When running commands such as kubectl get tkr or kubectl get kr, only older VKr versions appear, and the expected newer versions are missing.
This issue occurs when the Content Library has not synchronized recently, preventing vCenter from pulling the latest VKr images
vCenter is unable to reach or synchronize with the subscribed Content Library. Without a successful sync, new images are not downloaded, and the list of VKr versions cannot be updated.
Restore connectivity between vCenter and the subscribed Content Library (e.g., addressing DNS, firewall, routing, proxy, storage, or network path issues).
Once the Content Library synchronizes successfully, the expected VKr versions will be pulled and will appear in VKS as intended.