Explicitly set foundryvtt pod hostname#34
Open
LiquidPL wants to merge 1 commit intomahahe-it:mainfrom
Open
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
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.
Foundry uses the hostname to check whether the user has already accepted the license agreement. Because Deployment pod names are randomized, this will cause Foundry to show the license prompt every time the pod is recreated, such as when draining the node to upgrade.
Alternatively this could be fixed using a StatefulSet instead of a Deployment, but that would require non-insignificant refactoring of the pod, and besides, fixing the hostname like that shouldn't cause any issues since Foundry doesn't support running multiple copies at once.