Skip to content

Commit 03dfe5d

Browse files
SimonTheLegSimonTheLeg
authored
document workaround for bitnami registry deprecation (kubermatic#1956)
* document workaround for bitnami registry deprecation * remove main, as this issue will not occur in newer versions
1 parent e741482 commit 03dfe5d

File tree

3 files changed

+117
-0
lines changed

3 files changed

+117
-0
lines changed

‎content/kubermatic/v2.26/architecture/known-issues/_index.en.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,3 +52,42 @@ For an explanation how to configure an other oidc provider than dex take a look
5252
### security implications regarding dex solution
5353
5454
For dex this has some implications. With this configuration a token is generated for each user session. The number of objects stored in kubernetes regarding refresh tokens has no limit anymore. The principle that one refresh belongs to one user/client pair is a security consideration which would be ignored in that case. The only way to revoke a refresh token is then to do it via grpc api which is not exposed by default or by manually deleting the related refreshtoken resource in the kubernetes cluster.
55+
56+
## Workaround for the Bitnami registry changes if upgrade is not possible
57+
58+
Customers who are completely unable to upgrade to KKP patch version 2.26.12 or above, may use a workaround.
59+
This should be treated as a last resort method and comes with downsides on future upgrades. Specifically, with the patch releases, we are also moving to mirrored helm-charts to ensure stability and independence going forward. This workaround will not migrate to the mirrored charts, it will only switch images.
60+
61+
Workaround in detail:
62+
63+
1. Add the following to your mla values.yaml at the top level:
64+
65+
```yaml
66+
cortex:
67+
memcached-blocks-index:
68+
image:
69+
registry: quay.io
70+
repository: kubermatic-mirror/images/memcached
71+
metrics:
72+
image:
73+
registry: quay.io
74+
repository: kubermatic-mirror/images/memcached-exporter
75+
memcached-blocks:
76+
image:
77+
registry: quay.io
78+
repository: kubermatic-mirror/images/memcached
79+
metrics:
80+
image:
81+
registry: quay.io
82+
repository: kubermatic-mirror/images/memcached-exporter
83+
memcached-blocks-metadata:
84+
image:
85+
registry: quay.io
86+
repository: kubermatic-mirror/images/memcached
87+
metrics:
88+
image:
89+
registry: quay.io
90+
repository: kubermatic-mirror/images/memcached-exporter
91+
```
92+
93+
2. Re-run the mla installation process in accordance with the [official documentation](../../tutorials-howtos//monitoring-logging-alerting//user-cluster/admin-guide/#installing-mla-stack-in-a-seed-cluster) with a kubermatic installer matching your current KKP version.

‎content/kubermatic/v2.27/architecture/known-issues/_index.en.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,3 +52,42 @@ For an explanation how to configure an other oidc provider than dex take a look
5252
### security implications regarding dex solution
5353
5454
For dex this has some implications. With this configuration a token is generated for each user session. The number of objects stored in kubernetes regarding refresh tokens has no limit anymore. The principle that one refresh belongs to one user/client pair is a security consideration which would be ignored in that case. The only way to revoke a refresh token is then to do it via grpc api which is not exposed by default or by manually deleting the related refreshtoken resource in the kubernetes cluster.
55+
56+
## Workaround for the Bitnami registry changes if upgrade is not possible
57+
58+
Customers who are completely unable to upgrade to KKP patch version 2.27.7 or above, may use a workaround.
59+
This should be treated as a last resort method and comes with downsides on future upgrades. Specifically, with the patch releases, we are also moving to mirrored helm-charts to ensure stability and independence going forward. This workaround will not migrate to the mirrored charts, it will only switch images.
60+
61+
Workaround in detail:
62+
63+
1. Add the following to your mla values.yaml at the top level:
64+
65+
```yaml
66+
cortex:
67+
memcached-blocks-index:
68+
image:
69+
registry: quay.io
70+
repository: kubermatic-mirror/images/memcached
71+
metrics:
72+
image:
73+
registry: quay.io
74+
repository: kubermatic-mirror/images/memcached-exporter
75+
memcached-blocks:
76+
image:
77+
registry: quay.io
78+
repository: kubermatic-mirror/images/memcached
79+
metrics:
80+
image:
81+
registry: quay.io
82+
repository: kubermatic-mirror/images/memcached-exporter
83+
memcached-blocks-metadata:
84+
image:
85+
registry: quay.io
86+
repository: kubermatic-mirror/images/memcached
87+
metrics:
88+
image:
89+
registry: quay.io
90+
repository: kubermatic-mirror/images/memcached-exporter
91+
```
92+
93+
2. Re-run the mla installation process in accordance with the [official documentation](../../tutorials-howtos//monitoring-logging-alerting//user-cluster/admin-guide/#installing-mla-stack-in-a-seed-cluster) with a kubermatic installer matching your current KKP version.

‎content/kubermatic/v2.28/architecture/known-issues/_index.en.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,3 +112,42 @@ spec:
112112
```
113113

114114
This sets `--xfr-channel-size=300` flag for Konnectivity Agent, which runs on the user cluster.
115+
116+
## Workaround for the Bitnami registry changes if upgrade is not possible
117+
118+
Customers who are completely unable to upgrade to KKP patch version 2.28.2 or above, may use a workaround.
119+
This should be treated as a last resort method and comes with downsides on future upgrades. Specifically, with the patch releases, we are also moving to mirrored helm-charts to ensure stability and independence going forward. This workaround will not migrate to the mirrored charts, it will only switch images.
120+
121+
Workaround in detail:
122+
123+
1. Add the following to your mla values.yaml at the top level:
124+
125+
```yaml
126+
cortex:
127+
memcached-blocks-index:
128+
image:
129+
registry: quay.io
130+
repository: kubermatic-mirror/images/memcached
131+
metrics:
132+
image:
133+
registry: quay.io
134+
repository: kubermatic-mirror/images/memcached-exporter
135+
memcached-blocks:
136+
image:
137+
registry: quay.io
138+
repository: kubermatic-mirror/images/memcached
139+
metrics:
140+
image:
141+
registry: quay.io
142+
repository: kubermatic-mirror/images/memcached-exporter
143+
memcached-blocks-metadata:
144+
image:
145+
registry: quay.io
146+
repository: kubermatic-mirror/images/memcached
147+
metrics:
148+
image:
149+
registry: quay.io
150+
repository: kubermatic-mirror/images/memcached-exporter
151+
```
152+
153+
2. Re-run the mla installation process in accordance with the [official documentation](../../tutorials-howtos//monitoring-logging-alerting//user-cluster/admin-guide/#installing-mla-stack-in-a-seed-cluster) with a kubermatic installer matching your current KKP version.

0 commit comments

Comments
 (0)