-
Notifications
You must be signed in to change notification settings - Fork 165
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
procedures: Add readiness init container docs (#2139)
Add readiness init container docs Co-authored-by: Anatolii Bazko <abazko@redhat.com> Co-authored-by: Mickey Maler <mmaler@redhat.com> Co-authored-by: Max Leonov <mleonov@redhat.com> Co-authored-by: tstastna <78429689+tstastna@users.noreply.github.com> Co-authored-by: Fabrice Flore-Thébault <ffloreth@redhat.com> Co-authored-by: Robert Krátký <rkratky@redhat.com> Co-authored-by: Nick Boldt <nboldt@redhat.com> Co-authored-by: che-bot <39771996+che-bot@users.noreply.github.com> Co-authored-by: Mykhailo Kuznietsov <mkuznets@redhat.com>
- Loading branch information
1 parent
5abc60a
commit 62ffbe2
Showing
15 changed files
with
236 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 6 additions & 0 deletions
6
...tion-guide/pages/disabling-readiness-init-containers-for-the-olm-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[id="disabling-readiness-init-containers-for-the-olm-installer"] | ||
:navtitle: Disabling the readiness init containers for the OLM installer | ||
:keywords: disable-readiness-init-containers, disabling-readiness-init-containers, init-container, readiness-init-container, startup, olm | ||
:page-aliases: .:disabling-readiness-init-containers-for-the-olm-installer | ||
|
||
include::partial$proc_disabling-readiness-init-containers-for-the-olm-installer.adoc[] |
6 changes: 6 additions & 0 deletions
6
...guide/pages/disabling-readiness-init-containers-for-the-operator-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[id="disabling-readiness-init-containers-for-the-operator-installer"] | ||
:navtitle: Disabling the readiness init containers for the Operator installer | ||
:keywords: disable-readiness-init-containers, disabling-readiness-init-containers, init-container, readiness-init-container, startup, operator | ||
:page-aliases: .:disabling-readiness-init-containers-for-the-operator-installer | ||
|
||
include::partial$proc_disabling-readiness-init-containers-for-the-operator-installer.adoc[] |
6 changes: 6 additions & 0 deletions
6
...ges/enabling-and-disabling-readiness-init-containers-for-the-olm-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[id="enabling-and-disabling-readiness-init-containers-for-the-olm-installer"] | ||
:navtitle: Enabling and disabling the readiness init containers for the OLM installer | ||
:keywords: enable-readiness-init-containers, disable-readiness-init-containers, enabling-readiness-init-containers, disabling-readiness-init-containers, init-container, readiness-init-container, startup, olm | ||
:page-aliases: .:enabling-and-disabling-readiness-init-containers-for-the-olm-installer | ||
|
||
include::partial$assembly_enabling-and-disabling-readiness-init-containers-for-the-olm-installer.adoc[] |
6 changes: 6 additions & 0 deletions
6
...nabling-and-disabling-readiness-init-containers-for-the-operator-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[id="enabling-and-disabling-readiness-init-containers-for-the-operator-installer"] | ||
:navtitle: Enabling and disabling the readiness init containers for the Operator installer | ||
:keywords: enable-readiness-init-containers, disable-readiness-init-containers, enabling-readiness-init-containers, disabling-readiness-init-containers, init-container, readiness-init-container, startup, operator | ||
:page-aliases: .:enabling-and-disabling-readiness-init-containers-for-the-operator-installer | ||
|
||
include::partial$assembly_enabling-and-disabling-readiness-init-containers-for-the-operator-installer.adoc[] |
6 changes: 6 additions & 0 deletions
6
...ation-guide/pages/enabling-readiness-init-containers-for-the-olm-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[id="enabling-readiness-init-containers-for-the-olm-installer"] | ||
:navtitle: Enabling the readiness init containers for the OLM installer | ||
:keywords: enable-readiness-init-containers, enabling-readiness-init-containers, init-container, readiness-init-container, startup, olm | ||
:page-aliases: .:enabling-readiness-init-containers-for-the-olm-installer | ||
|
||
include::partial$proc_enabling-readiness-init-containers-for-the-olm-installer.adoc[] |
6 changes: 6 additions & 0 deletions
6
...-guide/pages/enabling-readiness-init-containers-for-the-operator-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[id="enabling-readiness-init-containers-for-the-operator-installer"] | ||
:navtitle: Enabling the readiness init containers for the Operator installer | ||
:keywords: enable-readiness-init-containers, enabling-readiness-init-containers, init-container, readiness-init-container, startup, operator | ||
:page-aliases: .:enabling-readiness-init-containers-for-the-operator-installer | ||
|
||
include::partial$proc_enabling-readiness-init-containers-for-the-operator-installer.adoc[] |
6 changes: 6 additions & 0 deletions
6
modules/administration-guide/pages/readiness-init-containers.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[id="readiness-init-containers"] | ||
:navtitle: Readiness init containers | ||
:keywords: init-container, readiness-init-container, startup | ||
:page-aliases: .:readiness-init-containers | ||
|
||
include::partial$assembly_readiness-init-containers.adoc[] |
13 changes: 13 additions & 0 deletions
13
...bly_enabling-and-disabling-readiness-init-containers-for-the-olm-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
:parent-context-of-enabling-and-disabling-readiness-init-containers-for-the-olm-installer: {context} | ||
|
||
[id="enabling-and-disabling-readiness-init-containers-for-the-olm-installer_{context}"] | ||
= Enabling and disabling the readiness init containers for the OLM installer | ||
|
||
:context: enabling-and-disabling-readiness-init-containers-for-the-olm-installer | ||
|
||
You can enable and disable the readiness init containers for the {prod-short} installed by the OLM installer. (Available through `{prod-cli}`, the OLM installer uses the Operator Lifecycle Manager to install {prod-short}.) | ||
|
||
* xref:enabling-readiness-init-containers-for-the-olm-installer.adoc[Enabling the readiness init containers for the OLM installer] | ||
* xref:disabling-readiness-init-containers-for-the-olm-installer.adoc[Disabling the readiness init containers for the OLM installer] | ||
|
||
:context: {parent-context-of-enabling-and-disabling-readiness-init-containers-for-the-olm-installer} |
13 changes: 13 additions & 0 deletions
13
...nabling-and-disabling-readiness-init-containers-for-the-operator-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
:parent-context-of-enabling-and-disabling-readiness-init-containers-for-the-operator-installer: {context} | ||
|
||
[id="enabling-and-disabling-readiness-init-containers-for-the-operator-installer_{context}"] | ||
= Enabling and disabling the readiness init containers for the Operator installer | ||
|
||
:context: enabling-and-disabling-readiness-init-containers-for-the-operator-installer | ||
|
||
You can enable and disable the readiness init containers for the {prod-short} installed by the Operator installer: | ||
|
||
* xref:enabling-readiness-init-containers-for-the-operator-installer.adoc[Enabling the readiness init containers for the Operator installer] | ||
* xref:disabling-readiness-init-containers-for-the-operator-installer.adoc[Disabling the readiness init containers for the Operator installer] | ||
|
||
:context: {parent-context-of-enabling-and-disabling-readiness-init-containers-for-the-operator-installer} |
16 changes: 16 additions & 0 deletions
16
modules/administration-guide/partials/assembly_readiness-init-containers.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
:parent-context-of-readiness-init-containers: {context} | ||
|
||
[id="readiness-init-containers_{context}"] | ||
= Readiness init containers | ||
|
||
:context: readiness-init-containers | ||
|
||
{prod-short} Operator installs {prod-short} and starts its containers in the correct order. If a node with {prod-short} is restarted and all {prod-short} containers start simultaneously, some containers may fail because some other component they depend on is not ready. To avoid such failures, the readiness init containers queue the containers for {prod-short} components to start in the correct order. | ||
|
||
The readiness init containers are disabled by default. If you choose to enable them, proceed according to the installation method used to install {prod-short}: | ||
|
||
* xref:enabling-and-disabling-readiness-init-containers-for-the-operator-installer.adoc[] | ||
|
||
* xref:enabling-and-disabling-readiness-init-containers-for-the-olm-installer.adoc[] | ||
|
||
:context: {parent-context-of-readiness-init-containers} |
42 changes: 42 additions & 0 deletions
42
...de/partials/proc_disabling-readiness-init-containers-for-the-olm-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
:_module-type: PROCEDURE | ||
|
||
[id="disabling-readiness-init-containers-for-the-olm-installer_{context}"] | ||
= Disabling the readiness init containers for the OLM installer | ||
|
||
To disable the previously enabled readiness init containers for the {prod-short} installed by the OLM installer: | ||
|
||
.Prerequisites | ||
|
||
* {prod-short} is installed by the OLM installer. | ||
|
||
.Procedure | ||
|
||
. Find the {prod-short} Operator subscription name: | ||
+ | ||
[source,shell,subs="+quotes,+attributes"] | ||
---- | ||
$ {orch-cli} get subscriptions -n {prod-namespace} | ||
---- | ||
|
||
. Get the CSV (Cluster Service Version) name from the {prod-short} Operator subscription: | ||
+ | ||
[source,shell,subs="+quotes,+attributes"] | ||
---- | ||
$ {orch-cli} get subscription <subscription-name> -n {prod-namespace} -o yaml | grep installedCSV | ||
---- | ||
|
||
. Edit the `ClusterServiceVersion` YAML manifest: | ||
+ | ||
[source,shell,subs="+quotes,+attributes"] | ||
---- | ||
$ {orch-cli} edit csv _<csv-name>_ -n {prod-namespace} | ||
---- | ||
. Remove the following environment variable from the Operator Deployment spec: | ||
+ | ||
[source,yaml,subs="+quotes,+attributes"] | ||
---- | ||
- name: ADD_COMPONENT_READINESS_INIT_CONTAINERS | ||
value: "true" | ||
---- | ||
|
||
. Wait for the {prod-short} Operator restart to finish. The restarted Operator will then continue with restarting some of its components. |
28 changes: 28 additions & 0 deletions
28
...rtials/proc_disabling-readiness-init-containers-for-the-operator-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
[id="disabling-readiness-init-containers-for-the-operator-installer_{context}"] | ||
= Disabling the readiness init containers for the Operator installer | ||
|
||
To disable the previously enabled readiness init containers for the {prod-short} installed by the Operator installer: | ||
|
||
.Prerequisites | ||
|
||
* {prod} installed by the Operator installer. | ||
|
||
.Procedure | ||
|
||
. Find the name of the {prod-short} Operator Deployment. Usually it is `{prod-id-short}-operator`: | ||
+ | ||
[source,yaml,subs="+quotes,+attributes"] | ||
---- | ||
$ {orch-cli} get deployments -n {prod-namespace} | ||
---- | ||
|
||
. Edit the Deployment as follows: Under `spec.template.spec.containers[0].env` of the Operator Deployment, remove the following lines: | ||
+ | ||
[source,yaml,subs="+quotes,+attributes"] | ||
---- | ||
- name: ADD_COMPONENT_READINESS_INIT_CONTAINERS <1> | ||
value: "true" | ||
---- | ||
<1> `ADD_COMPONENT_READINESS_INIT_CONTAINERS` is an environment variable. | ||
|
||
. Wait while {prod-short} Operator restarts some components. |
44 changes: 44 additions & 0 deletions
44
...ide/partials/proc_enabling-readiness-init-containers-for-the-olm-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
:_module-type: PROCEDURE | ||
|
||
[id="enabling-readiness-init-containers-for-the-olm-installer_{context}"] | ||
= Enabling the readiness init containers for the OLM installer | ||
|
||
The readiness init containers are not enabled by default, so to use them you first have to enable them. To enable the readiness init containers for the {prod-short} installed by the OLM installer: | ||
|
||
.Prerequisites | ||
|
||
* {prod-short} is installed by the OLM installer. | ||
|
||
.Procedure | ||
|
||
. Find the {prod-short} Operator subscription name: | ||
+ | ||
[source,shell,subs="+quotes,+attributes"] | ||
---- | ||
$ {orch-cli} get subscriptions -n {prod-namespace} | ||
---- | ||
|
||
. Get the CSV (Cluster Service Version) name from the {prod-short} Operator subscription: | ||
+ | ||
[source,shell,subs="+quotes,+attributes"] | ||
---- | ||
$ {orch-cli} get subscription <subscription-name> -n {prod-namespace} -o yaml | grep installedCSV | ||
---- | ||
|
||
. Edit the `ClusterServiceVersion` YAML manifest: | ||
+ | ||
[source,shell,subs="+quotes,+attributes"] | ||
---- | ||
$ {orch-cli} edit csv _<csv-name>_ -n {prod-namespace} | ||
---- | ||
. Add the following environment variable to the Operator Deployment spec: | ||
+ | ||
[source,yaml,subs="+quotes,+attributes"] | ||
---- | ||
- name: ADD_COMPONENT_READINESS_INIT_CONTAINERS | ||
value: "true" | ||
---- | ||
|
||
. Wait for the {prod-short} Operator restart to finish. The restarted Operator will then continue with restarting some of its components. | ||
|
||
NOTE: Repeat these steps after each {prod-short} upgrade when a new CSV is created by OLM. |
30 changes: 30 additions & 0 deletions
30
...artials/proc_enabling-readiness-init-containers-for-the-operator-installer.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
[id="enabling-readiness-init-containers-for-the-operator-installer_{context}"] | ||
= Enabling the readiness init containers for the Operator installer | ||
|
||
The readiness init containers are not enabled by default, so to use them you first have to enable them. To enable the readiness init containers for the {prod-short} installed by the Operator installer: | ||
|
||
.Prerequisites | ||
|
||
* {prod} installed by the Operator installer. | ||
|
||
.Procedure | ||
|
||
. Find the name of the {prod-short} Operator Deployment. Usually it is `{prod-id-short}-operator`: | ||
+ | ||
[source,yaml,subs="+quotes,+attributes"] | ||
---- | ||
$ {orch-cli} get deployments -n {prod-namespace} | ||
---- | ||
|
||
. Edit the Deployment as follows: Under `spec.template.spec.containers[0].env` of the Operator Deployment, insert the following lines: | ||
+ | ||
[source,yaml,subs="+quotes,+attributes"] | ||
---- | ||
- name: ADD_COMPONENT_READINESS_INIT_CONTAINERS <1> | ||
value: "true" | ||
---- | ||
<1> `ADD_COMPONENT_READINESS_INIT_CONTAINERS` is an environment variable. | ||
|
||
. Wait while {prod-short} Operator restarts some components. | ||
|
||
NOTE: Repeat these steps after each {prod-short} upgrade when a new Operator Deployment is created. |