release-23.1: roachprod: bump max DNS results limit #124117
Merged
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.
Backport 1/1 commits from #121047.
/cc @cockroachdb/release
The
gcloud
DNS commands filter after retrieving results, set by the limit, and not before, since the API call itself has no concept of a filter. This means the limit has to be higher to ensure the full list is retrieved, before thegcloud
command filters. Currently, we are getting nearer to the 1000 limit, hence this change bumps it to 10000 to avoid possible future problems.Epic: None
Release Note: None
Release justification: Test only change.