Skip to content
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.

Sign up for GitHub

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

Jump to bottom

decide which approach to use in the NATS-manager (declarative, helm, etc) #3

Closed
Tracked by #14
k15r opened this issue Mar 7, 2023 · 1 comment
Closed
Tracked by #14

decide which approach to use in the NATS-manager (declarative, helm, etc) #3

k15r opened this issue Mar 7, 2023 · 1 comment
Assignees
@friedrichwilken
Labels
area/eventing Issues or PRs related to eventing

Comments

@k15r
Copy link
Contributor

k15r commented Mar 7, 2023 •
edited by marcobebway

Before we start to implement the NATS manager we need to figure out which provisioning approach we want to use for provisioning NATS resources using the manager.

Options are:

  • declarative
  • helm
  • imperative

Questions to answer:

  • which approach looks most promising for maintenance / upgrade from upstream nats-repos
@k15r k15r mentioned this issue Mar 21, 2023
Closed
18 tasks
@k15r k15r changed the title decide on architecture decide which approach to use in the NATS-manager (declarative, helm, etc) Mar 7, 2023
@friedrichwilken friedrichwilken self-assigned this Mar 7, 2023
@k15r k15r transferred this issue from kyma-project/kyma Mar 8, 2023
@friedrichwilken friedrichwilken removed their assignment Mar 9, 2023
@mfaizanse mfaizanse added the area/eventing Issues or PRs related to eventing label Mar 13, 2023
@friedrichwilken friedrichwilken self-assigned this Mar 13, 2023
@k15r
Copy link
Contributor Author

k15r commented Mar 17, 2023

Helm seems to be the most practical approach for the NATS manager. We will use the helm charts provided by nats and apply them with minimal changes to the cluster using the manager.

@k15r k15r closed this as completed Mar 17, 2023
@marcobebway marcobebway mentioned this issue Mar 17, 2023
Closed
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@friedrichwilken friedrichwilken

Labels
area/eventing Issues or PRs related to eventing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@k15r @mfaizanse @friedrichwilken