Add k8s cronjobs testing in CI
What does this MR do and why?
Introduce a new test in CI to test cronjobs. For each cronjob we create a job and check if it complete
Related reference(s)
close #1312 (closed)
need !3304 (merged) to be merged, otherwise
cattle-fleet-system fleet-cleanup-gitrepo-jobs @daily False 0 13h 5d2h
fleet-default rke2-machineconfig-cleanup-cronjob 5 0 * * * False 1 13h 5d2h
related jobs failed to start due to missing security context
Test coverage
CI configuration
CI pipelines perform an update for both management and workload clusters, this update will NOT perform a ClusterAPI rolling update (deletion and creation of new K8s nodes) by default.
For some cases, it may be relevant to perform more complex tests.
Theses features can be activated in an MR by adding one of these labels to the MR and will apply to the next pipelines.
- adding the label ci-featuretest-rolling-update pipelines will perform a node rolling update in the
-updatejobs (without version upgrades) - adding the label ci-featuretest-upgrade-from-1.1.1 pipelines will perform an upgrade from Sylva 1.1.1 to your dev branch (including a k8s version upgrade resulting in a node rolling update)