-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated channel server response breaks Rancher Desktop #11447
Comments
brandond
added a commit
to brandond/channelserver
that referenced
this issue
Dec 9, 2024
Rancher Desktop and other projects were relying on the collection type to be plural: k3s-io/k3s#11447 Ref: * rancher@4e582e2 * rancher/apiserver@1045731 Signed-off-by: Brad Davidson <[email protected]>
brandond
added a commit
to rancher/channelserver
that referenced
this issue
Dec 10, 2024
Rancher Desktop and other projects were relying on the collection type to be plural: k3s-io/k3s#11447 Ref: * 4e582e2 * rancher/apiserver@1045731 Signed-off-by: Brad Davidson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
resourceType
field of the channel server response used to bechannels
, but has changed tochannel
sometime late last week:This unfortunately breaks Rancher Desktop 1.16 (the latest public release), which checks the
resourceType
: rancher-sandbox/rancher-desktop#7461This means on any new installation of Rancher Desktop, as well as any time a user performs a factory reset that wipes the k3s cache, the list of available k3s versions will be empty and the user cannot enable Kubernetes.
The text was updated successfully, but these errors were encountered: