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

Add a design document for User customization and Persistence #2233

Closed
Ebaneck opened this issue Feb 12, 2020 · 0 comments
Closed

Add a design document for User customization and Persistence #2233

Ebaneck opened this issue Feb 12, 2020 · 0 comments
Assignees
@Ebaneck
Labels
kind:design Solution design choices topic:docs Documentation topic:operations Operations-related issues

Comments

@Ebaneck
Copy link
Contributor

Ebaneck commented Feb 12, 2020 •
edited
Loading

Component:

'docs'

Why this is needed:

Our new approach warrants that for each new feature being developed, we provide a good, well written and validated design document.

This will be a follow up to the requirements document from #2232

What should be done:

Implementation proposal (strongly recommended):

Test plan:

Epic: #1996
@Ebaneck Ebaneck added kind:design Solution design choices topic:docs Documentation topic:operations Operations-related issues labels Feb 12, 2020
Ebaneck added a commit that referenced this issue Feb 13, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
43a6f8e 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 13, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
cc9bf97 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
@Ebaneck Ebaneck mentioned this issue Feb 13, 2020
Merged
Ebaneck added a commit that referenced this issue Feb 14, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
3fbc9ad 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 14, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
82d5c04 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 14, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
5d2a994 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 14, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
f4349b2 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 14, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
4c85252 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 17, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
5288ebf 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 17, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
e55466e 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 17, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
b969b2b 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 17, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
a53edb5 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 17, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
8a087e9 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 17, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
76d4f89 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 18, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
87653ce 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 18, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
490f9a2 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 18, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
fa766e1 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 18, 2020
@Ebaneck
doc: Add a design doc for user customization & persistence
7c2fc38 
Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Feb 24, 2020
@Ebaneck
doc: Add a design doc for the persistence of cluster and service conf…
899106f 
…igurations

Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
@Ebaneck Ebaneck mentioned this issue Feb 24, 2020
Closed
@Ebaneck Ebaneck self-assigned this Feb 24, 2020
Ebaneck added a commit that referenced this issue Feb 26, 2020
@Ebaneck
doc: Add a design doc for the persistence of cluster and service conf…
ee1193e 
…igurations

Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
@Ebaneck Ebaneck added the topic: cluster&service configuration Anything related to cluster and service configuration persistence label Feb 26, 2020
Ebaneck added a commit that referenced this issue Feb 26, 2020
@Ebaneck
doc: Add a design doc for the persistence of cluster and service conf…
e7c1e66 
…igurations

Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
@thomasdanan thomasdanan mentioned this issue Feb 27, 2020
Closed
@Ebaneck Ebaneck removed the topic: cluster&service configuration Anything related to cluster and service configuration persistence label Feb 27, 2020
Ebaneck added a commit that referenced this issue Feb 27, 2020
@Ebaneck
doc: Add a design doc for the persistence of cluster and service conf…
6586e23 
…igurations

Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
Ebaneck added a commit that referenced this issue Mar 3, 2020
@Ebaneck
doc: Add a design doc for the persistence of cluster and service conf…
8407ee2 
…igurations

Initially, user defined configurations such as changing the number of
replicas for a given deployment in a MetalK8s cluster are lost during
an upgrade/downgrade scenario.

This document explains some of the design choices considered while
designing a simplistic tool for MetalK8s that guarantees that user defined
configurations are persisted throughout.

Closes: #2233
@bert-e bert-e closed this as completed in 990dc34 Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Ebaneck Ebaneck

Labels
kind:design Solution design choices topic:docs Documentation topic:operations Operations-related issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Ebaneck