Conversation
Scaled to 0. It was kept as a fallback for NRP outages, but served no real traffic -- 5 requests in 24h, all crawler hits on /, favicon.ico and robots.txt, no API calls -- while holding a public hostname and needing upkeep. Set replicas back to 2 to restore.
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
1 participant
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.
Scales the cirrus deployment to 0, matching what is now live in the cluster.
Why
This copy existed as a fallback for if NRP went down. On reflection that is not a good reason to keep a second deployment running: it holds a public hostname and needs upkeep, in exchange for standby capacity nobody was using.
It was also genuinely idle. Over 24 h it logged 5 requests, all crawler traffic:
No API calls at all.
Scope
Only
replicaschanges. The Service, Ingress and the rest of the manifest are untouched and still correct, so restoring is settingreplicas: 2and re-applying — the comment in the file says so.The NRP-facing deployment (the actual purpose of this proxy: GLEN models plus CORS and request logging for web access) is unaffected.