chore(cloud-init): truncate hostnames in determineHostname#1
Merged
RiRa12621 merged 1 commit intoflatcar-masterfrom Apr 3, 2025
Merged
chore(cloud-init): truncate hostnames in determineHostname#1RiRa12621 merged 1 commit intoflatcar-masterfrom
RiRa12621 merged 1 commit intoflatcar-masterfrom
Conversation
Too long hostname are not allowed and potentially breaking things. Instead of individually checking the hostname in each metadata provider, we adjust the hostname length when it's used to be set
RiRa12621
force-pushed
the
rira12621-hostname-truncate
branch
from
84e115b to
33c483b
Compare
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.
truncate too long hostnames
Long hostnames can have unexpected consequences and this makes the truncation behavior explicit
This also cleans up existing truncating in AWS
How to use
A new node that uses cloud init and has an overly long host name.
Technically the second case should never happen, because most cloud providers are attempting to block direct instance names longer than 63 chars, but rather safe than sorry.
Testing done
Test added for
..is still too longchangelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.This is an alternative to flatcar#30
In this suggestion, all truncation happens centrally instead of for each metadata service. This reduces code duplication.