Skip to content
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

Closed
jandubois opened this issue Dec 9, 2024 · 1 comment
Closed

Updated channel server response breaks Rancher Desktop #11447

jandubois opened this issue Dec 9, 2024 · 1 comment

Comments

@jandubois
Copy link

jandubois commented Dec 9, 2024

The resourceType field of the channel server response used to be channels, but has changed to channel sometime late last week:

$ curl --silent --fail https://update.k3s.io/v1-release/channels | jq 'del(.data)'
{
  "type": "collection",
  "links": {
    "self": "https://update.k3s.io/v1-release/channels"
  },
  "actions": {},
  "resourceType": "channel"
}

This unfortunately breaks Rancher Desktop 1.16 (the latest public release), which checks the resourceType: rancher-sandbox/rancher-desktop#7461

This 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.

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]>
@brandond
Copy link
Member

brandond commented Dec 10, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done Issue
Development

No branches or pull requests

2 participants