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

Cluster and Services Configuration & Persistence #1996

Closed
thomasdanan opened this issue Nov 5, 2019 · 0 comments
Closed

Cluster and Services Configuration & Persistence #1996

thomasdanan opened this issue Nov 5, 2019 · 0 comments
Labels
kind:epic High-level description of a feature iteration topic:operations Operations-related issues

Comments

@thomasdanan
Copy link
Contributor

thomasdanan commented Nov 5, 2019

Abstract:

We require a unified design (as much as possible) to provide means for cluster administrators to configure the deployment, and have these settings persisted under common operations (upgrade/downgrade, reboots, restoration procedures...).

Example settings:

  • Number of replicas for addons (Prometheus, Alertmanager, Grafana, Dex...)
  • Dex configuration
  • Alert/Rules configuration
  • etc ...
@gdemonet gdemonet added kind:epic High-level description of a feature iteration topic:operations Operations-related issues labels Nov 5, 2019
@gdemonet gdemonet mentioned this issue Jan 22, 2020
1 task
@gdemonet gdemonet changed the title User Customization & Persistence Cluster and Services Configuration & Persistence Feb 18, 2020
gdemonet pushed a commit that referenced this issue Feb 20, 2020
First list of requirements for the topic of 'Cluster and Services
Configurations & Persistence'.

This focuses on high-level requirements, and provides a first list of
settings a cluster administrator should be able to configure.

Issue: #2232
Epic: #1996
gdemonet pushed a commit that referenced this issue Feb 20, 2020
First list of requirements for the topic of 'Cluster and Services
Configurations & Persistence'.

This focuses on high-level requirements, and provides a first list of
settings a cluster administrator should be able to configure.

Issue: #2232
Epic: #1996
@thomasdanan thomasdanan added this to the MetalK8s 2.6.0 milestone Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:epic High-level description of a feature iteration topic:operations Operations-related issues
Projects
None yet
Development

No branches or pull requests

2 participants