Skip to content

K8SPS-496 Documented the CR option to disable NodePort allocation for… - #203

Merged
nastena1606 merged 1 commit into
mainfrom
K8SPS-496-Allow-disable-nodePort-allocation
Jul 3, 2026
Merged

K8SPS-496 Documented the CR option to disable NodePort allocation for…#203
nastena1606 merged 1 commit into
mainfrom
K8SPS-496-Allow-disable-nodePort-allocation

Conversation

@nastena1606

Copy link
Copy Markdown
Collaborator

… Services

modified: docs/operator.md

@nastena1606
nastena1606 requested a review from Copilot June 22, 2026 14:54
@it-percona
it-percona temporarily deployed to K8SPS-496-Allow-disable-nodePort-allocation - percona-mysql-operator-ps PR #203 June 22, 2026 14:54 — with Render Destroyed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the operator documentation to describe the CR fields that control whether Kubernetes allocates NodePorts for Services of type LoadBalancer, allowing users to disable NodePort allocation where supported.

Changes:

  • Documented allocateLoadBalancerNodePorts for MySQL primary exposure (mysql.exposePrimary.*) and per-Pod exposure (mysql.expose.*).
  • Documented allocateLoadBalancerNodePorts for HAProxy, Router, and Orchestrator exposure Service configurations.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@nastena1606 nastena1606 added the pending release PR is ready to be included in the upcoming release label Jun 29, 2026
@nastena1606
nastena1606 merged commit 3f1709e into main Jul 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pending release PR is ready to be included in the upcoming release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants