Upgrade kubespray fork to 2.29.0-ck8s

[linus-elastisys]

Warning

This is a public repository, ensure not to disclose:

• personal data beyond what is necessary for interacting with this pull request, nor
• business confidential information, such as customer names.

What kind of PR is this?

Required: Mark one of the following that is applicable:

• kind/feature
• kind/improvement
• kind/deprecation
• kind/documentation
• kind/clean-up
• kind/bug
• kind/other

Optional: Mark one or more of the following that are applicable:

Important

Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

• kind/admin-change
• kind/dev-change
• kind/security
• [kind/adr](set-me)

Platform Administrator notice

• The default Kubernetes version has been bumped to 1.33.5.
• In Kubespray playbooks: the master tag has been removed and is replaced by control-plane.

What does this PR do / why do we need this PR?

Updates Kubespray to upstream version 2.29.

• Part of [3] Upgrade to kubespray v2.29 #472

Information to reviewers

Tested an upgrade from 2.28 -> 2.29 on a Safespring cluster, and things seems to work well. No errors during the upgrade, and apps are running fine both before and after the upgrade.

As far as I can tell, there's no relevant Kubernetes 1.33 changes, or Kubespray 2.29 changes that needs to be included as admin-change or dev-change.

Checklist

• Proper commit message prefix on all commits
• Change checks:
  • The change is transparent
  • The change is disruptive
  • The change requires no migration steps
  • The change requires migration steps
• Documentation checks:
  • The public documentation required no updates
  • The public documentation required an update - [link to change](set-me)
• Metrics checks:
  • The metrics are still exposed and present in Grafana after the change
  • The metrics names didn't change (Grafana dashboards and Prometheus alerts required no updates)
  • The metrics names did change (Grafana dashboards and Prometheus alerts required an update)
• Logs checks:
  • The logs do not show any errors after the change
• PodSecurityPolicy checks:
  • Any changed Pod is covered by Kubernetes Pod Security Standards
  • Any changed Pod is covered by Gatekeeper Pod Security Policies
  • The change does not cause any Pods to be blocked by Pod Security Standards or Policies
• NetworkPolicy checks:
  • Any changed Pod is covered by Network Policies
  • The change does not cause any dropped packets in the NetworkPolicy Dashboard
• Audit checks:
  • The change does not cause any unnecessary Kubernetes audit events
  • The change requires changes to Kubernetes audit policy
• Falco checks:
  • The change does not cause any alerts to be generated by Falco
• Bug checks:
  • The bug fix is covered by regression tests

[linus-elastisys]

Just tried an upgrade from 2.28 -> 2.29 on a Safespring cluster, and things seems to work well. No errors during the upgrade, and apps are running fine both before and after the upgrade.

As far as I can tell, there's no relevant Kubernetes 1.33 changes, or Kubespray 2.29 changes that needs to be included as admin-change or dev-change.

[Xartos]

Could you add to the PR the admin release notes that the default kubernetes version is bumped and that the master tag is now removed. I think we might have some docs that assumes that tag exists

[linus-elastisys]

Could you add to the PR the admin release notes that the default kubernetes version is bumped and that the master tag is now removed. I think we might have some docs that assumes that tag exists

Thanks, fixed now.