Validate new version

[ghost]

Explain problem to solve

Validate last 3 version.
Because we only validate cluster api release and never cluster api config.

Describe the solution you would like

Options 1:

• Validate with conformance test, security test l and clusterctl template last 3 version of kubernetes each month.

Options2:

• Detect new version of kubernetes and launch conformance and security test.

Additional context

None

Environment

- Kubernetes version: (use `kubectl version`): v1.22.5-rancher1-1
- OS (e.g. from `/etc/os-release`): CentOS Linux 7 (Core)
- Kernel (e.g. `uname -a`): 3.10.0-1160.15.2.el7.x86_64
- cluster-api-provider-outscale version: v1.1.3
- cluster-api version: current
- Install tools: calico, ingress-nginx, osc-ccm
- Kubernetes Distribution: rke
- Kubernetes Distribution version: v1.3.4

[ghost]

Page pour comprendre les autres providers.

[ghost]

Regarder la différences entre les conf (kustomize ?)

[pierreozoux]

Hi,

I'm upgrading my cluster.

Currently running 1.22.

I have this output:

outscale@ip-10-0-xx:~$ clusterctl upgrade plan
Checking new release availability...

Latest release available for the v1beta1 API Version of Cluster API (contract):

NAME                      NAMESPACE                              TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm         capi-kubeadm-bootstrap-system          BootstrapProvider        v1.4.2            v1.6.0
control-plane-kubeadm     capi-kubeadm-control-plane-system      ControlPlaneProvider     v1.4.2            v1.6.0
cluster-api               capi-system                            CoreProvider             v1.4.2            v1.6.0
infrastructure-outscale   cluster-api-provider-outscale-system   InfrastructureProvider   v0.2.4            v0.3.0

My plan is to update to k8s 1.28

Reading this https://cluster-api.sigs.k8s.io/reference/versions#kubeadm-bootstrap-provider-kubeadm-bootstrap-controller

My plan is to first update to 1.26.
Then, I'll update clusterctl compiled from this repo. And do a clusterctl upgrade plan && cluster upgrade apply.

I miss the compatibility matrix between this repo, the releases (current 0.3.0) and compatibility with cluster-api version and k8s version.

Thanks for your help!