Repository navigation
Enable public listing compression and selective log retention in production - #1799
Merged
Merged
Conversation
This branch was previously deployed
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.
Enable negotiated gzip for credential-free public listing responses and 10% retention of fast successful listing access logs, using the implementation in #1798. Preserve errors, slow reads, retries, authentication and publishing routes, audit logs and unsampled metrics. Application templates, cache lifetime, database resources and capacity remain unchanged.
Document the narrowly scoped deployment role needed to manage this exclusion. The existing deployment service accounts have only get/list/create/update exclusion permissions through that additional role; no log or bucket deletion permission is added.
Validation: live staging encoding, identity fallback and decoded-content checks passed; bounded read probes, CPU/throttling checks and service health passed. A later sample after log-router propagation confirmed selective retention. Repository CI and the exact-head production saved-plan preview passed; the plan permits only the ingress ConfigMap, its in-place update provider setting and the named exclusion. Detailed evidence remains private.