What steps did you take and what happened:
clusterctl upgrade plane -v 10
[I] clusterctl upgrade plan -v 10
No default config file available
Checking cert-manager version...
Cert-Manager is already up to date
Checking new release availability...
Fetching File="metadata.yaml" Provider="cluster-api" Version="v0.3.10"
Fetching File="metadata.yaml" Provider="bootstrap-talos" Version="v0.2.0-alpha.6"
Fetching File="metadata.yaml" Provider="control-plane-talos" Version="v0.1.0-alpha.8"
Fetching File="metadata.yaml" Provider="cluster-api" Version="v0.3.10"
Fetching File="metadata.yaml" Provider="infrastructure-sidero" Version="v0.1.0-alpha.9"
Management group: capi-system/cluster-api, latest release available for the v1alpha3 API Version of Cluster API (contract):
NAME NAMESPACE TYPE CURRENT VERSION NEXT VERSION
bootstrap-talos cabpt-system BootstrapProvider v0.2.0-alpha.6 Already up to date
control-plane-talos cacppt-system ControlPlaneProvider v0.1.0-alpha.8 Already up to date
cluster-api capi-system CoreProvider v0.3.10 Already up to date
infrastructure-sidero sidero-system InfrastructureProvider v0.1.0-alpha.8 Already up to date
You are already up to date!
No default config file available
What did you expect to happen:
Sidero infra provider to be planned for an upgrade.
Anything else you would like to add:
Environment:
[I] clusterctl version
clusterctl version: &version.Info{Major:"0", Minor:"3", GitVersion:"v0.3.10", GitCommit:"af6630920560ca0e12179897b96d6ea8bd830b63", GitTreeState:"clean", BuildDate:"2020-10-01T14:29:50Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
kubectl version):[I] kubectl version
Client Version: version.Info{Major:"1", Minor:"19+", GitVersion:"v1.19.0-rc.2", GitCommit:"27bb2a4a0a5cb8330178d19e57fa61fffa895c98", GitTreeState:"clean", BuildDate:"2020-07-21T17:39:35Z", GoVersion:"go1.14.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
/etc/os-release):[I] talosctl read /etc/os-release --nodes 10.5.0.2
NAME="Talos"
ID=talos
VERSION_ID=v0.7.0-beta.0
PRETTY_NAME="Talos (v0.7.0-beta.0)"
HOME_URL="https://docs.talos-systems.com/"
BUG_REPORT_URL="https://github.com/talos-systems/talos/issues"
/kind bug
/area upgrades
/assign @wfernandes @fabriziopandini
@andrewrynhard Thanks for filing this issue.
As per our documentation, clusterctl upgrade plan by default does not consider pre-release versions.
However, you can still upgrade to the specified pre-release as follows. See here for more details.
clusterctl upgrade apply --management-group capi-system/cluster-api \
--core capi-system/cluster-api:v0.3.10 \
--bootstrap capi-kubeadm-bootstrap-system/kubeadm:v0.3.10 \
--control-plane capi-kubeadm-control-plane-system/kubeadm:v0.3.10 \
--infrastructure sidero-system/sidero:v0.1.0-alpha.9
Most helpful comment
@andrewrynhard Thanks for filing this issue.
As per our documentation,
clusterctl upgrade planby default does not consider pre-release versions.However, you can still upgrade to the specified pre-release as follows. See here for more details.