rancher / rke

Rancher Kubernetes Engine (RKE), an extremely simple, lightning fast Kubernetes distribution that runs entirely within containers.
Apache License 2.0
3.2k stars 580 forks source link

Calico versions and other CNI version info? Where? #3555

Open BloodyIron opened 5 months ago

BloodyIron commented 5 months ago

I can't for the life of me figure out where RKE1 documentation exists that outlines which versions of CNIs, such as Calico, are used by which versions of RKE1. And I can't seem to figure it out from the code really.

Where is this information kept? I really need to reference it. Thanks!

BloodyIron commented 4 months ago

Seriously there's no resources on this information? This seems like a pretty substantial oversight for Documentation...

manuelbuil commented 4 months ago

I'm an RKE2 developer, so maybe I'm wrong, but if I remember correctly, I normally check versions with rke config --list-version --all

pgonin commented 4 months ago

Have you considered RKE2 instead of RKE? https://docs.rke2.io/networking/basic_network_options

BloodyIron commented 4 months ago

Have you considered RKE2 instead of RKE? https://docs.rke2.io/networking/basic_network_options

I would rather have documentation for the tech I'm using instead of just switching tech. I tried RKE2 previously and had issues with it, I don't recall this moment what they were. But my ask is completely reasonable. RKE2 has this aspect documented, where's the same for RKE1?

BloodyIron commented 4 months ago

I'm an RKE2 developer, so maybe I'm wrong, but if I remember correctly, I normally check versions with rke config --list-version --all

I want to know the versions before I switch so that I know what targets to aim for. I can't check for a version I'm not running. I can check the versions of the running calico pods just fine, that's not what I'm asking for. I'm asking for documentation that outlines the expected CNI versions (in my case Calico) that are used by the different RKE1 versions. Asking for documentation of this (which is present for RKE2, but I'm using RKE1 and am not interested in switching at this time) is perfectly reasonable.

xcezz commented 4 months ago

Are you looking for https://github.com/rancher/kontainer-driver-metadata/blob/dev-v2.8/pkg/rke/k8s_rke_system_images.go?

Source: https://rke.docs.rancher.com/config-options/system-images

github-actions[bot] commented 2 months ago

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

BloodyIron commented 2 months ago

Are you looking for https://github.com/rancher/kontainer-driver-metadata/blob/dev-v2.8/pkg/rke/k8s_rke_system_images.go?

Source: https://rke.docs.rancher.com/config-options/system-images

Neither of those sources of information are updated, accurate, or even easy to find. While that is topically relevant, that's really not a proper solution to the absence that exists.

github-actions[bot] commented 6 days ago

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.