chore: remove init containers for startup order#253
Merged
Conversation
Signed-off-by: Nic <qianyong@api7.ai>
ronething
approved these changes
Feb 9, 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
2 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.
Although these init containers reduce some error logs during the initial startup, when a deployed cluster fails, they cannot be recovered independently due to interdependencies between components. For example, if prometheus fails, it will prevent the dashboard from starting, and if the dashboard fails, it will in turn prevent dpm and portal from starting. However, in reality, a prometheus failure only affects observability-related functions, and there is no strong dependency between the dashboard and dpm & portal; they can run completely independently.