fix wrong template rendering on cilium_ip_masq_agent_enable variable

[mahjonp]

Signed-off-by: mahjonp [email protected]

What type of PR is this?

/kind bug

What this PR does / why we need it:

I make a mistake on #8893 as @we10710aa say, hope it hasn't cause too much trouble.

Which issue(s) this PR fixes:

#8893 (comment)

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @mahjonp. 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.

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/test-infra repository.

[cristicalin]

Thanks for fixing this @mahjonp !

/ok-to-test
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cristicalin, mahjonp

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [cristicalin]

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

[oomichi]

Thanks for fixing the issue.

/lgtm

[cristicalin]

/ok-to-test

[we10710aa]

@mahjonp Thank you for your help.
Can you backport this into 2.19 branch? It would be nice taht this get fixed within v2.19

[we10710aa]

@oomichi Also, I think this should be added to known issue in release page

[mahjonp]

@mahjonp Thank you for your help. Can you backport this into 2.19 branch? It would be nice taht this get fixed within v2.19

Of course