fix: integrate inotify parameter setup into environmentSetup deploy flow#135
Open
DasAbin wants to merge 4 commits into
Open
fix: integrate inotify parameter setup into environmentSetup deploy flow#135DasAbin wants to merge 4 commits into
DasAbin wants to merge 4 commits into
Conversation
Replace destructive /etc/hosts perl rewrites with an idempotent Gazelle sentinel block so redeployments refresh only Gazelle-managed host entries and never overwrite existing 127.0.0.1 mappings. Made-with: Cursor
Revert commit 8d58c46 per request. Made-with: Cursor
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.
Problem
vnext pods hit EMFILE (CrashLoopBackOff) on fresh Ubuntu deploys because
inotify limits are too low. A fix script existed at
src/utils/test-scripts/increase-inotify-params-untested.sh but was never
called from the main deploy flow.
Fix
Tested
Verified on AWS EC2 t3.xlarge Ubuntu 24.04 — sysctl values confirmed set,
vnext pods Running without EMFILE errors.
Closes: referenced in #gazelle-dev Slack discussion