Document the tolerations deprecation and fix the dev nodeSelector notes

[rberrelleza]

Problem

The Okteto Helm chart has warned since 1.21 that these values are deprecated:

[WARNING] .Values.tolerations.[oktetoPool, devPool, buildPool] is deprecated
and will be removed in Okteto Chart 2.0.

The docs have never carried that deprecation. There is no reference entry for these values, the word "deprecated" appears on the Helm configuration page only under the unrelated autoscaler heading, and the migration guide is reachable only from the chart's install-time output. Meanwhile two runnable examples on the page still teach the deprecated form, so the docs are actively producing new users of a value scheduled for removal.

Changes

• Deprecation warning under globals.tolerations, linking the community migration guide.
• daemonset example updated from tolerations.devPool to globals.nodeSelectors / globals.tolerations.
• Removed an orphaned code block in the defaultBackend section. It was a bare tolerations: devPool: dev snippet with no surrounding prose, immediately after the "Custom error pages" bullet, and reads as a copy-paste artifact.
• Corrected the dev nodeSelector coupling notes (4 places, see below).
• Fixed a factual error: a note instructed users to "define a devPool entry in globals.tolerations". No such key exists; globals.tolerations takes okteto and dev. Following it literally produces an invalid config.

On the coupling claim

The page stated, in four places, that globals.nodeSelectors.dev only applies when tolerations.devPool is also set, described as legacy behavior.

That is worth a careful look because it is self-contradictory: it tells users to keep setting the value the chart says is being removed. It also does not match observed behavior.

Verified on a live GKE cluster running chart 1.47.0, configured entirely with the new form so that the configmap carried OKTETO_DEV_POOL: "":

• OKTETO_GLOBAL_NODE_SELECTORS: {"dev":{"okteto-node-pool":"dev"},"okteto":{"okteto-node-pool":"okteto"}}
• Every user pod in an Okteto-managed namespace still received nodeSelector: {"okteto-node-pool":"dev"} plus the matching toleration, and scheduled onto the dev pool. Confirmed with a scratch namespace and separately with a real okteto deploy of an 8-service app.

So the dev node selectors are applied unconditionally. What was genuinely gated on devPool is the auto-generated taint toleration, which is why the replacement notes now tell you to spell out globals.tolerations.dev when the target nodes are tainted.

Please sanity-check this against the backend, since it is the one change here based on observed behavior rather than on the chart source.

Not changed

The autoscaler section still says "Use tolerations.devPool to limit the autoscaler analysis to a subset of cluster nodes." I left it alone: the autoscaler is deprecated and disabled by default, and I could not verify whether it reads the new values. Worth a follow-up from whoever owns it.

Related

Complements #1328, which documents the ingress-nginx default-certificate override. Both touch helm-configuration.mdx, so the second to merge will need a trivial rebase.

Applied to both src/content and versioned_docs/version-1.47, which were byte-identical beforehand and remain in sync.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for okteto-docs ready!

Name	Link
🔨 Latest commit	5c33339
🔍 Latest deploy log	https://app.netlify.com/projects/okteto-docs/deploys/6a7f3adcf2e1970008369d9b
😎 Deploy Preview	https://deploy-preview-1329--okteto-docs.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.

[rberrelleza]

Added one more commit: regcredsManager.replicas was undocumented. Every other component uses replicaCount, so setting replicaCount everywhere silently leaves this one at 2. Small and adjacent enough that a third PR seemed like noise, but happy to split it out if you'd rather.

[rberrelleza]

Correction to my earlier comment: regcredsManager.replicas was already documented in that section, I just missed it. I've reverted that commit, so this PR is back to the tolerations deprecation and the dev nodeSelector notes only.