Merged
Conversation
github-actions
bot
added
Component: Content Author
Contributor
|
Will potential future deploys require CA to be added manually after first deploy? |
Contributor
Author
|
Yes. There are a number of ways this could be solved, but I think we should cross that bridge when we get there. For now, let's just remove the script to prevent CA being added over and over. |
Kamelon7
approved these changes
Mar 13, 2025
maxmoeschinger
approved these changes
Mar 13, 2025
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
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.
first-time-setup-completedfile in the non-persistent volume, this would result in CA being added over and over every time new instances were created.443/udpis unnecessary.