Skip to content

Use default values in RamenConfig#2433

Draft
ELENAGER wants to merge 5 commits intoRamenDR:mainfrom
ELENAGER:DFBUGS-440
Draft

Use default values in RamenConfig#2433
ELENAGER wants to merge 5 commits intoRamenDR:mainfrom
ELENAGER:DFBUGS-440

Conversation

@ELENAGER
Copy link
Member

No description provided.

@nirs
Copy link
Member

nirs commented Feb 25, 2026

_ No description provided. _

?

@ELENAGER
Copy link
Member Author

@nirs it is still a draft. I created it to work with @raghavendra-talur

@nirs
Copy link
Member

nirs commented Feb 25, 2026

If we move controller type to env variable, we need to change also ramenctl - it expects to find the controller type in the config and will fail cluster validate without a controller type.
https://github.com/RamenDR/ramenctl/blob/f925e0dc753f784425ee836f56d8bca3516c4396/pkg/validate/clusters.go#L461

ramenctl can extract the controller type from deployment but it is harder than using the config, and it is not consistent when some values come from the config and some from the environment. We need a good reason to split configuration in env and config.

@ELENAGER ELENAGER force-pushed the DFBUGS-440 branch 2 times, most recently from 5c25ad3 to 56a1ba4 Compare March 2, 2026 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants