This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
fix: loggregator DNS spam #365
Merged
Conversation
This file contains 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
added 2 commits
January 27, 2020 13:55
Centralized all release management into a single file for easier maintainability.
It fixes the loggregator spam to the DNS server.
f0rmiga
added
Type: Bug
mook-as
approved these changes
Jan 27, 2020
bikramnehra
pushed a commit
that referenced
this pull request
Apr 21, 2020
fix: loggregator DNS spam
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
This fixes the loggregator DNS spam by rolling the release version back from 106 to 105. Also, refactors the release versioning ops-files for easier maintainability.
Motivation and Context
As noted by many people, the newest loggregator release has an issue related to too many DNS requests. E.g. cloudfoundry/loggregator-release#401.
How Has This Been Tested?
Deployed kubecf with the changes including Eirini and app-autoscaler. Then, I checked that the DNS was not being spammed.
Types of changes
Checklist: