Repository navigation
skills: Redpanda Cloud skill updates (2026-11-05) - #124
Merged
Merged
Conversation
A cluster PATCH that names only `throughput_tier` keeps the cluster's current broker count, and that count is validated against the target tier. A move to a smaller tier is therefore refused with `node count too high for current throughput tier` over a broker count the request never mentioned, and the fix is to set `redpanda_node_count` in the same request rather than to retry the tier change alone. The scaling section presented the broker-count maximum as a check on a count the caller supplies, so an agent reading a node-count error on a tier-only request would have had no way to place it. Record the sources for the rule in the file header and the source map. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Scaling a BYOC cluster to a different machine type without naming a broker count keeps the cluster's current broker count, and that count is checked against the tier being moved to. A move to a smaller tier can therefore be rejected for a broker count the request never mentioned, which the cloud-byoc scaling guidance did not account for: it now states the rule, the error a caller gets, and that the fix is to set the broker count in the same request.