Skip to content

Allow external nats #151

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Allow external nats #151

wants to merge 1 commit into from

Conversation

geekgonecrazy
Copy link
Contributor

Adds new properties:
microservices.nats.enabled this turns nats deployment off and on
microservices.nats.existingSecret this allows you to create a secret holding your nats connectionString inside

@geekgonecrazy geekgonecrazy requested a review from debdutdeb June 6, 2024 20:30
Comment on lines 299 to +305
microservices:
enabled: false

nats:
enabled: true
existingSecret: ''

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so the reason I hadn't added this yet was this.

Due to nats deployment being connected to microservices.enabled, we need nats.enabled set to true (as is here) for existing ms deployments to not break on update.

On the other hand, this will cause monolithic deployments to suddenly create nats deployments without needing it.

I guess it's not a big deal - however will need communication so folks can disable this afterwards.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can change to

    condition: microservices.enabled, nats.enabled

Helm 3 (release 2019) supports this. Basically, we would have to enable both at the same time, and if either of them is false, then it is not deployed (but need more testing)

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.

3 participants