docs: document internal load balancer requirements for private web services#270
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document internal load balancer requirements for private web services#270mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Clarifies how Porter handles private (internal load balancer) web services now that internal-LB availability is discovered live from each cluster rather than assumed.
Context
Upstream change ships per-cluster discovery of ingress endpoints. The internal load-balancer option is now only offered on clusters where the controller is actually installed, and app create/update is rejected (
invalid_load_balancer_mode) whenprivate: trueis set on a cluster that lacks the controller. Private services also use a different CNAME target than public services, surfaced per-service in the Networking tab.Changes
applications/configuration-as-code/services/web-service.mdx: Expanded theprivatefield reference with prerequisites, the dashboard gating behavior, the validation error users may hit, and a note that the CNAME target differs from public services.applications/configure/custom-domains.mdx: Added a callout that public and private services have different load-balancer hostnames, and that switching a service's mode requires updating the DNS record.