Open gwadson opened 4 months ago
@gwadson:
If you have chance, could you you please run the following command:
$ k get pods -n system-upgrade
A normal output would be 1/1 READY
What's happening, I think, is that the path of the update controller we are currently using, links to an image which is no longer available. But we could use the update controller from the official k3s docs. Note that the URL is different.
---
hetzner_token: <your token>
cluster_name: test
kubeconfig_path: "./kubeconfig"
k3s_version: v1.26.4+k3s1
public_ssh_key_path: "~/.ssh/id_rsa.pub"
private_ssh_key_path: "~/.ssh/id_rsa"
use_ssh_agent: false # ...
ssh_allowed_networks:
- 0.0.0.0/0
api_allowed_networks:
- 0.0.0.0/0
private_network_subnet: 10.0.0.0/16
disable_flannel: false
schedule_workloads_on_masters: false
system_upgrade_controller_manifest_url: "https://raw.githubusercontent.com/rancher/system-upgrade-controller/v0.13.4/manifests/system-upgrade-controller.yaml"
masters_pool:
instance_type: cpx21
instance_count: 3
location: nbg1
Thanks @michaelfresco - I will see if I can update the tool this coming week to handle this properly.
I have fixed the setup of the System Upgrade Controller in main and this fix will come with the next release. I have tested fine but if any of you has a chance to double check that it's working as expected that would be nice.
Hi, Thanks for the project and your efforts really amazing.
I having issue to upgrade. no matter the version I'm getting the following error:
After Installation this are the CRD availble
Any Idea what could be the reason? Thank you