Document operator autoscaling and tuning#949
Merged
Merged
Conversation
Add subsections to the operator deploy guide covering HorizontalPodAutoscaler config, resource and Go runtime tuning, and OpenShift support with no special configuration. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Kubernetes operator deployment guide to cover operator-level operational tuning, including autoscaling, resource sizing, Go runtime GC/memory tuning, and OpenShift behavior.
Changes:
- Added documentation for enabling operator HorizontalPodAutoscaler (
operator.autoscaling) and its metrics-server prerequisite. - Documented operator resource requests/limits defaults and Go runtime tuning via
operator.gc(GOMEMLIMIT,GOGC). - Added an OpenShift section explaining the operator’s platform detection and security context adjustments for restricted SCCs.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jhrozek
approved these changes
Jun 18, 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
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.
Description
Documents operator-level tuning in
deploy-operator.mdx:operator.autoscaling, disabled by default).operator.gcforGOMEMLIMIT/GOGC).Helm value paths and defaults were verified against the operator chart (
deploy/charts/operator/values.yaml), and the OpenShift behavior against the operator source (DetectPlatform/SecurityContextBuilder).Note: the original gap analysis in #655 listed operator feature flags (
ENABLE_SERVER/ENABLE_REGISTRY/ENABLE_AGGREGATIONandcrds.install.virtualMCP). Those are intentionally not documented: the implementing PR (stacklok/toolhive#2729) was closed unmerged, and the values do not exist in the current chart.Type of change
Related issues/PRs
Addresses gaps in #655.
Submitter checklist
Content and formatting
Reviewer checklist
Content