feat: new, shorter hash function for k8s resource names #141
Conversation
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
ValentinGerlach
force-pushed
the
k8s-object-hashes-2
branch
3 times, most recently
from
52bd3fa to
4514bcd
Compare
robertgraeff
force-pushed
the
k8s-object-hashes-2
branch
from
4514bcd to
bce4329
Compare
Diaphteiros
approved these changes
Sep 11, 2025
n3rdc4ptn
approved these changes
Sep 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What this PR does / why we need it:
We added new hash functions for Kubernetes resource names in #114. Unfortunately, the UUID format turned out to be too long in many cases. This PR adds a shorter variant. It still uses SHAKE128 (SHA-3) which is FIPS 202 compliant. The output (40 bits) is base32 encoded so it can be used in names for other Kubernetes resources.
Release note: