fix: pin auth-config ConfigMap name via fullnameOverride#21
Merged
rpignolet merged 1 commit intoJul 3, 2026
Merged
Conversation
f2f8445 to
8ade7b5
Compare
idirze
approved these changes
Jul 3, 2026
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
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
Seaweedfs s3 pod mounts the IAM auth ConfigMap by hardcoded name
{{ .Realease.metadata.name }}-auth-config. Some deployment release names get random suffix (eg.seaweedfs-ijyinorseaweedfs-qyocqo) wich does not contain the substringseaweedfs-auth-configexpected by the dedup logic to triggerRelated Issue
Fixes #20
Type of Change
How to Test
In order to confirm the fix works, the seaweedfs pod should be in running state instead of containerCreating and the config map should have the correct name expected by the dedup logic in the helper.
Checklist