You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/registry-removed.adoc
+2-15Lines changed: 2 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,19 +18,6 @@
18
18
[id="registry-removed_{context}"]
19
19
= Image registry removed during installation
20
20
21
-
On platforms that do not provide shareable object storage, the OpenShift Image
22
-
Registry Operator bootstraps itself as `Removed`. This allows
23
-
`openshift-installer` to complete installations on these platform types.
21
+
On platforms that do not provide shareable object storage, the OpenShift Image Registry Operator bootstraps itself as `Removed`. This allows `openshift-installer` to complete installations on these platform types.
24
22
25
-
After installation, you must edit the Image Registry Operator configuration to
26
-
switch the `managementState` from `Removed` to `Managed`.
27
-
28
-
[NOTE]
29
-
====
30
-
The Prometheus console provides an `ImageRegistryRemoved` alert, for example:
31
-
32
-
"Image Registry has been removed. `ImageStreamTags`, `BuildConfigs` and
33
-
`DeploymentConfigs` which reference `ImageStreamTags` may not work as
34
-
expected. Please configure storage and update the config to `Managed`
35
-
state by editing configs.imageregistry.operator.openshift.io."
36
-
====
23
+
After installation, you must edit the Image Registry Operator configuration to switch the `managementState` from `Removed` to `Managed`.
0 commit comments