Skip to content

Stop relying only on isHubCluster to enable the unsealJob #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2025

Conversation

mbaldessari
Copy link
Contributor

Eventually we would like to drop isHubCluster as it is confusing and its
meaning does not always make sense (think of a standalone mcg setup.
I.e. one without ACM at all).

So let's enable the unsealJob either when isHubCluster is set to true
(in order to not break compatibility) or when in the application we
have the "hashicorp-vault" chart.

Tested on a standalone target for mcg and everything worked correctly.

Eventually we would like to drop isHubCluster as it is confusing and its
meaning does not always make sense (think of a standalone mcg setup.
I.e. one without ACM at all).

So let's enable the unsealJob either when isHubCluster is set to true
(in order to not break compatibility) or when in the application we
have the "hashicorp-vault" chart.

Tested on a standalone target for mcg and everything worked correctly.
@mbaldessari mbaldessari merged commit 0e0e3a4 into validatedpatterns:main Feb 6, 2025
3 checks passed
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.

1 participant