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

Replace various metalk8s-* storageclass by a single metalk8s one #2742

Closed
alexandre-allard opened this issue Aug 14, 2020 · 1 comment · Fixed by #2760
Closed

Replace various metalk8s-* storageclass by a single metalk8s one #2742

alexandre-allard opened this issue Aug 14, 2020 · 1 comment · Fixed by #2760
Assignees
Labels
complexity:easy Something that requires less than a day to fix

Comments

@alexandre-allard
Copy link
Contributor

Component: salt, addons, docs

Why this is needed:
Today we have 1 metalk8s-prometheus (prometheus & alertmanager) and 1 metalk8s-loki (loki & fluent-bit) storageclass, but it does not make sense as the storageclass name must not be used to define the purpose of it.
Moreover, these class are exactly the same, so there is no point of keeping both.

What should be done:
Replace metalk8s-prometheus and metalk8s-loki storageclass everywhere by a metalk8s one.

Implementation proposal (strongly recommended):
Should be updated in examples, docs and salt

Test plan:
Tests should still work.

@alexandre-allard alexandre-allard added the complexity:easy Something that requires less than a day to fix label Aug 14, 2020
@TeddyAndrieux
Copy link
Collaborator

NOTE: Right now in Loki chart you cannot provide any selector for volume so for the moment we consider all volume with storage class metalk8s-loki as Loki volume check this commit message 97cd2ff

@alexandre-allard alexandre-allard self-assigned this Aug 24, 2020
alexandre-allard added a commit that referenced this issue Aug 24, 2020
We know use a single metalk8s storageclass
for all addons as it does not make sense in K8s
to select storage by storageclass name.
We use label selector to get the right PV.

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 24, 2020
Use the new metalk8s storageclass instead of the
old metalk8s-prometheus one.

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 24, 2020
Delete during prometheus-operator post upgrade cleanup

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 24, 2020
Delete during prometheus-operator post upgrade

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 25, 2020
We know use a single metalk8s storageclass
for all addons as it does not make sense in K8s
to select storage by storageclass name.
We use label selector to get the right PV.

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 25, 2020
Use the new metalk8s storageclass instead of the
old metalk8s-prometheus one.

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 25, 2020
Delete during prometheus-operator post upgrade

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 25, 2020
We now use a single metalk8s storageclass
instead of one per addon (e.g. metalk8s-loki).

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 25, 2020
This is needed as Loki chart only allow to
target a PV with its storageclass name and
we now use a single storageclass for all addons.

This change needs to be ported upstream so
we can still upgrade Loki chart.

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 25, 2020
This also adds a label on the PV so that we can
now select the PV based on this label instead
of the storageclass name.

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 26, 2020
We now use a single metalk8s storageclass
instead of one per addon (e.g. metalk8s-loki).

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 26, 2020
This is needed as Loki chart only allow to
target a PV with its storageclass name and
we now use a single storageclass for all addons.

This change needs to be ported upstream so
we can still upgrade Loki chart.

Refs: #2742
alexandre-allard added a commit that referenced this issue Aug 26, 2020
This also adds a label on the PV so that we can
now select the PV based on this label instead
of the storageclass name.

Refs: #2742
ChengYanJin pushed a commit that referenced this issue Sep 3, 2020
We know use a single metalk8s storageclass
for all addons as it does not make sense in K8s
to select storage by storageclass name.
We use label selector to get the right PV.

Refs: #2742
ChengYanJin pushed a commit that referenced this issue Sep 3, 2020
Use the new metalk8s storageclass instead of the
old metalk8s-prometheus one.

Refs: #2742
ChengYanJin pushed a commit that referenced this issue Sep 3, 2020
Delete during prometheus-operator post upgrade

Refs: #2742
ChengYanJin pushed a commit that referenced this issue Sep 3, 2020
We now use a single metalk8s storageclass
instead of one per addon (e.g. metalk8s-loki).

Refs: #2742
ChengYanJin pushed a commit that referenced this issue Sep 3, 2020
This is needed as Loki chart only allow to
target a PV with its storageclass name and
we now use a single storageclass for all addons.

This change needs to be ported upstream so
we can still upgrade Loki chart.

Refs: #2742
ChengYanJin pushed a commit that referenced this issue Sep 3, 2020
This also adds a label on the PV so that we can
now select the PV based on this label instead
of the storageclass name.

Refs: #2742
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity:easy Something that requires less than a day to fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants