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
Fixes various issues in the docs. Mostly updates snippets to
reflect new fields from recent API changes.
Signed-off-by: Mikalai Radchuk <[email protected]>
Copy file name to clipboardExpand all lines: docs/concepts/upgrade-support.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,8 +63,8 @@ where setting the `upgradeConstraintPolicy` to:
63
63
64
64
OLM supports Semver to provide a simplified way for package authors to define compatible upgrades. According to the Semver standard, releases within a major version (e.g. `>=1.0.0 <2.0.0`) must be compatible. As a result, package authors can publish a new package version following the Semver specification, and OLM assumes compatibility. Package authors do not have to explicitly define upgrade edges in the catalog.
65
65
66
-
> [!NOTE]
67
-
> Currently, OLM 1.0 does not support automatic upgrades to the next major version. You must manually verify and perform major version upgrades. For more information about major version upgrades, see [Manually verified upgrades and downgrades](#manually-verified-upgrades-and-downgrades).
66
+
!!! note
67
+
Currently, OLM 1.0 does not support automatic upgrades to the next major version. You must manually verify and perform major version upgrades. For more information about major version upgrades, see [Manually verified upgrades and downgrades](#manually-verified-upgrades-and-downgrades).
Copy file name to clipboardExpand all lines: docs/contribute/developer.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,10 @@
3
3
4
4
The following `make run` starts a [KIND](https://sigs.k8s.io/kind) cluster for you to get a local cluster for testing, see the manual install steps below for how to run against a remote cluster.
5
5
6
-
> [!NOTE]
7
-
>You will need a container runtime environment, like Docker, or experimentally, Podman, installed, to run Kind.
8
-
>
9
-
>If you are on MacOS, see [Special Setup for MacOS](#special-setup-for-macos).
6
+
!!! note
7
+
You will need a container runtime environment, like Docker, or experimentally, Podman, installed, to run Kind.
8
+
9
+
If you are on MacOS, see [Special Setup for MacOS](#special-setup-for-macos).
10
10
11
11
### Quickstart Installation
12
12
@@ -20,9 +20,9 @@ This will build a local container image of the operator-controller, create a new
20
20
21
21
### To Install Any Given Release
22
22
23
-
> [!CAUTION]
24
-
>Operator-Controller depends on [cert-manager](https://cert-manager.io/). Running the following command
25
-
>may affect an existing installation of cert-manager and cause cluster instability.
23
+
!!! warning
24
+
Operator-Controller depends on [cert-manager](https://cert-manager.io/). Running the following command
25
+
may affect an existing installation of cert-manager and cause cluster instability.
26
26
27
27
The latest version of Operator Controller can be installed with the following command:
Copy file name to clipboardExpand all lines: docs/getting-started/olmv1_getting_started.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
3
3
The following script will install OLMv1 on a Kubernetes cluster. If you don't have one, you can deploy a Kubernetes cluster with [KIND](https://sigs.k8s.io/kind).
4
4
5
-
> [!CAUTION]
6
-
>Operator-Controller depends on [cert-manager](https://cert-manager.io/). Running the following command
7
-
>may affect an existing installation of cert-manager and cause cluster instability.
5
+
!!! warning
6
+
Operator-Controller depends on [cert-manager](https://cert-manager.io/). Running the following command
7
+
may affect an existing installation of cert-manager and cause cluster instability.
8
8
9
9
The latest version of Operator Controller can be installed with the following command:
10
10
@@ -44,7 +44,7 @@ spec:
44
44
type: Image
45
45
image:
46
46
ref: quay.io/operatorhubio/catalog:latest
47
-
pollInterval: 10m
47
+
pollIntervalMinutes: 10
48
48
EOF
49
49
```
50
50
@@ -78,7 +78,7 @@ and on the extension upgrade process [here](../tutorials/upgrade-extension.md).
0 commit comments