DOCS-2846: Add instruction for disabling upgrade-ipam

[ctauchen]

For manifest installs, you need to disable upgrade-ipam when
using host-local IPAM.

DOCS-2846

Product Version(s):

Issue:

projectcalico/calico#11702

Link to docs preview:

SME review:

• An SME has approved this change.

DOCS review:

• A member of the docs team has approved this change.

Additional information:

Merge checklist:

• Deploy preview inspected wherever changes were made
• Build completed successfully
• Test have passed

[netlify]

✅ Deploy Preview for calico-docs-preview-next ready!

Name	Link
🔨 Latest commit	6976512
🔍 Latest deploy log	https://app.netlify.com/projects/calico-docs-preview-next/deploys/698dc641cd83860008b893bb
😎 Deploy Preview	https://deploy-preview-2520--calico-docs-preview-next.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview succeeded!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	6976512
🔍 Latest deploy log	https://app.netlify.com/projects/tigera/deploys/698dc640ab88cb000817e90b
😎 Deploy Preview	https://deploy-preview-2520--tigera.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 68 (no change from production) Accessibility: 98 (no change from production) Best Practices: 92 (no change from production) SEO: 100 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[ctauchen]

@tomastigera Taking a first stab at this. Questions:

1. Does this apply only to manifest-based installations? Can I presume that the Operator handles this situation otherwise?
2. I've provided a one-liner to patch things. Are there better approaches?
3. The section this goes into doesn't say much by way of sequence. Is it important/better that this new step happens before or after any other step?

[Copilot]

Pull request overview

Adds documentation for Calico v3.31 manifest-based installs to clarify that upgrade-ipam should be disabled when using the CNI host-local IPAM mode, and provides a kubectl/jq command to remove the init container from the calico-node DaemonSet.

Changes:

• Document disabling the upgrade-ipam init container for manifest installs using host-local IPAM.
• Add a kubectl/jq example command to remove the init container from calico-node.

[Copilot]

For consistency with the rest of this section (and with the CNI plugin name), consider formatting host-local as inline code in this sentence.

Suggested change

	To use host-local IPAM on a manifest-based installation of $[prodname], you should disable the `upgrade-ipam` init container.
	To use `host-local` IPAM on a manifest-based installation of $[prodname], you should disable the `upgrade-ipam` init container.

[Copilot]

This new instruction is added only to the versioned v3.31 page; the unversioned (next/current) equivalent page at calico/reference/configure-cni-plugins.mdx still lacks the upgrade-ipam guidance. If this requirement applies generally (as implied by the PR title/description), it should also be added to the unversioned docs (and any other supported versions), or the PR description should clarify that this is a v3.31-only backport.

[Copilot]

The jq filter uses .spec.template.spec.initContainers[], which will error if initContainers is missing/null (for example if the init container was already removed). Consider making the command idempotent by using the optional iterator ([]?) or defaulting initContainers to an empty array before filtering.

Suggested change

	jq 'del(.spec.template.spec.initContainers[] | select(.name == "upgrade-ipam"))' | \
	jq 'del(.spec.template.spec.initContainers[]? | select(.name == "upgrade-ipam"))' | \