fix: starts of rotor without ClickHouse envs#1244
Open
Ogoyukin wants to merge 13 commits intojitsucom:newjitsufrom
Open
fix: starts of rotor without ClickHouse envs#1244Ogoyukin wants to merge 13 commits intojitsucom:newjitsufrom
Ogoyukin wants to merge 13 commits intojitsucom:newjitsufrom
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.
jitsucom/rotor fails to start in self-hosted deployments if ClickHouse environment variables are not defined, even when ClickHouse is not intended to be used.
When jitsu-clickhouse-secret is removed (or CLICKHOUSE_HOST / CLICKHOUSE_URL are not set), the rotor pod goes into CrashLoopBackOff with:
#1243