docs: clarify Divert shared environment must be Okteto-managed - #1333
Open
ekline[bot] wants to merge 1 commit into
Open
docs: clarify Divert shared environment must be Okteto-managed#1333ekline[bot] wants to merge 1 commit into
ekline[bot] wants to merge 1 commit into
Conversation
State across the Divert core concept, how-to, manifest reference, and tutorial that the shared environment must run in an Okteto-managed Namespace, and that a Namespace Okteto did not deploy is not a supported divert target. ekline[bot] <202747777+ekline[bot]@users.noreply.github.com> Signed-off-by: ekline[bot] <202747777+ekline[bot]@users.noreply.github.com>
ekline
Bot
requested review from
codyjlandstrom,
ifbyol,
pchico83 and
rlamana
as code owners
August 24, 2026 18:47
✅ Deploy Preview for okteto-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ifbyol
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Clarifies that Divert's shared environment must run in an Okteto-managed Namespace — a Namespace that Okteto deployed — and that pointing Divert at a Namespace Okteto did not deploy is not officially supported. This is the current official support position.
Prompted by a POV where a team asked whether Divert's shared environment could point to an existing
corenamespace they manage themselves (not deployed by Okteto). The docs described the shared environment only as "the shared namespace" / "an existing shared environment" without stating this boundary, leaving the answer ambiguous.Files
src/content/core/divert.mdx— new Shared environment requirements subsection under "How Divert Works", explaining the requirement and pointing users who run shared services outside Okteto to redeploy or duplicate them into an Okteto-managed Namespace.src/content/development/using-divert.mdx— note in the Manifest Configuration section and a clarification on thenamespacefield.src/content/reference/okteto-manifest.mdx— expanded thedivert.namespacefield description.src/tutorials/divert.mdx— reinforcing note in the shared-environment step.Why (grounded in behavior)
Divert routes traffic to services in the shared Namespace and, depending on the driver, reads or modifies their ingresses (nginx) or Istio VirtualServices, using the developer's Okteto credentials. Those credentials only reach Okteto Namespaces the developer can access, so in practice the shared Namespace must be an Okteto-managed Namespace. The wording deliberately matches the official support position rather than overstating an internal enforcement mechanism.
How to verify
get-started/deploy-your-app/deploy.mdx,previews/index.mdx).📝 Created with EkLine · View session