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.

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

Move Storage from daemon set to deployment #507

Open
3 tasks
SandGrainOne opened this issue Sep 26, 2024 · 0 comments
Open
3 tasks

Move Storage from daemon set to deployment #507

SandGrainOne opened this issue Sep 26, 2024 · 0 comments
Labels
kind/chore Typical issues like patching and deployment. status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@SandGrainOne
Copy link
Member

Description

There is a strong need to change what type of deployment Storage use. Daemon set is out date and not fit for purpose. Storage must be moved over to deployments.

Another change we include in this issue is the introduction of a namespace called storage that the Storage resources should be deployed to.

Additional Information

It's possible to configure deployments with affinities to spread the Storage pods across multiple nodes, but we will try without in the beginning. The less controll over how k8 organize the pods we enforce the better.

Tasks

  • Update helm charts to give Storage deployment instead of daemon set.
  • Update helm charts to create a new storage namespace where the Storage resources are deployed into

Acceptance Criterias

  • Storage runs
@SandGrainOne SandGrainOne added status/draft Status: When you create an issue before you have enough info to properly describe the issue. kind/chore Typical issues like patching and deployment. labels Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/chore Typical issues like patching and deployment. status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Development

No branches or pull requests

1 participant