cilium: render routingMode: native when cilium_tunnel_mode is disabled

[sinashahoveisi]

What type of PR is this?

/kind bug

What this PR does / why we need it

When cilium_tunnel_mode: disabled is set in inventory, the previous
template rendered tunnelProtocol: disabled in the Helm values.
Cilium does not recognize this value and falls back to vxlan, which
directly conflicts with routingMode: native and causes agents to
CrashLoopBackOff.

The fix renders routingMode: native instead when cilium_tunnel_mode
is disabled, matching the Cilium Helm chart API.

Which issue(s) this PR fixes

Related to issue 13267

Does this PR introduce a user-facing change?

Users no longer need to manually inject tunnelProtocol: "" via
cilium_extra_values. Setting cilium_tunnel_mode: disabled now
works as documented in defaults/main.yml.

Fix Cilium CrashLoopBackOff when cilium_tunnel_mode is set to disabled
by rendering routingMode: native instead of tunnelProtocol: disabled
in the Helm values.

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

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.

[linux-foundation-easycla]

• ❌ - login: @sinashahoveisi / name: sina shah oveisi. The commit (bdd56a6) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[k8s-ci-robot]

Welcome @sinashahoveisi!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @sinashahoveisi. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sinashahoveisi
Once this PR has been reviewed and has the lgtm label, please assign tico88612 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tico88612]

@sinashahoveisi could you checkout your CLA and release-note?

[sinashahoveisi]

Hi @tico88612, thank you for the review!

Unfortunately, as a contributor based in Iran, I am unable to sign the CLA due to OFAC compliance restrictions. I understand this is a blocker for merging.

Regarding the release-note, I will add it now.

[yankay]

/ok-to-test

[Copilot]

Pull request overview

This PR fixes Cilium Helm values rendering when cilium_tunnel_mode: disabled is configured, ensuring Kubespray emits the correct Cilium chart setting (routingMode: native) instead of an unsupported tunnelProtocol: disabled value that can lead to agent CrashLoopBackOff.

Changes:

• Render routingMode: native when cilium_tunnel_mode is set to disabled (otherwise keep rendering tunnelProtocol).
• Clarify cilium_tunnel_mode semantics in role defaults, including the disabled behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
roles/network_plugin/cilium/templates/values.yaml.j2	Adds conditional rendering to output routingMode: native when tunneling is disabled, aligning with the Cilium Helm chart API.
roles/network_plugin/cilium/defaults/main.yml	Updates comments to document valid tunnel mode values and explain the rendered Helm values behavior for disabled.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.