Kubespray release-2.24 (v2.24.1) issue with calico version v3.25.2

[hadi2f244]

What happened?

Error on installing calico v3.25.2 with kubespray release-2.24 (v2.24.1) because of the differences in calico manifests:

https://github.com/projectcalico/calico/issues/8825

What did you expect to happen?

Proper manifest for older calico version.

How can we reproduce it (as minimally and precisely as possible)?

Change calico_version to v3.25.2 in kubespray release-2.24 (v2.24.1). Related manifest file

OS

Linux 5.4.0-169-generic x86_64 Ubuntu 20.04.6 LTS (Focal Fossa) Calico V3.25.2 Kubespray release 2.24 (v2.24.1)

Version of Ansible

ansible [core 2.15.10] config file = None configured module search path = ['/home/hadi/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /home/hadi/kubespray/.venv/lib/python3.11/site-packages/ansible ansible collection location = /home/hadi/.ansible/collections:/usr/share/ansible/collections executable location = /home/hadi/kubespray/.venv//bin/ansible python version = 3.11.9 (main, Apr 6 2024, 17:59:24) [GCC 9.4.0] (/home/hadi/kubespray/.venv//bin/python3.11) jinja version = 3.1.2 libyaml = True

Version of Python

Python 3.11.9

Version of Kubespray (commit)

64447e7

Network plugin used

calico

Full inventory with variables

Default ones

Command used to invoke ansible

Output of ansible run

Anything else we need to know

No response

[hadi2f244]

I also compare calico installation manifest over V3.23.0 here:

calico_version_manifest_differences

As I know, Some of them can be disruptive like the one I mentioned between Calico v3.25.X and v3.26.X. Also, It also be possible for other templates and tools and If it is one of the Kubespray principles to contains all the manifests in the code, much better to automate it and find the upgrades in the tools installation manifests automatically to avoid such a simple inconsistency.

Related: https://github.com/kubernetes-sigs/kubespray/pull/10416#issuecomment-1713847205

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.