이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 10. Readiness init containers


CodeReady Workspaces Operator installs CodeReady Workspaces and starts its containers in the correct order. If a node with CodeReady Workspaces is restarted and all CodeReady Workspaces 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 CodeReady Workspaces 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 CodeReady Workspaces:

10.1. Enabling and disabling the readiness init containers for the Operator installer

You can enable and disable the readiness init containers for the CodeReady Workspaces installed by the Operator installer:

10.2. 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 CodeReady Workspaces installed by the Operator installer:

Prerequisites

  • Red Hat CodeReady Workspaces installed by the Operator installer.

Procedure

  1. Find the name of the CodeReady Workspaces Operator Deployment. Usually it is codeready-workspaces-operator:

    $ oc get deployments -n openshift-workspaces
    Copy to Clipboard Toggle word wrap
  2. Edit the Deployment as follows: Under spec.template.spec.containers[0].env of the Operator Deployment, insert the following lines:

     - name: ADD_COMPONENT_READINESS_INIT_CONTAINERS 
    1
    
       value: "true"
    Copy to Clipboard Toggle word wrap
    1
    ADD_COMPONENT_READINESS_INIT_CONTAINERS is an environment variable.
  3. Wait while CodeReady Workspaces Operator restarts some components.
Note

Repeat these steps after each CodeReady Workspaces upgrade when a new Operator Deployment is created.

10.3. Disabling the readiness init containers for the Operator installer

To disable the previously enabled readiness init containers for the CodeReady Workspaces installed by the Operator installer:

Prerequisites

  • Red Hat CodeReady Workspaces installed by the Operator installer.

Procedure

  1. Find the name of the CodeReady Workspaces Operator Deployment. Usually it is codeready-workspaces-operator:

    $ oc get deployments -n openshift-workspaces
    Copy to Clipboard Toggle word wrap
  2. Edit the Deployment as follows: Under spec.template.spec.containers[0].env of the Operator Deployment, remove the following lines:

     - name: ADD_COMPONENT_READINESS_INIT_CONTAINERS 
    1
    
       value: "true"
    Copy to Clipboard Toggle word wrap
    1
    ADD_COMPONENT_READINESS_INIT_CONTAINERS is an environment variable.
  3. Wait while CodeReady Workspaces Operator restarts some components.

10.4. Enabling and disabling the readiness init containers for the OLM installer

You can enable and disable the readiness init containers for the CodeReady Workspaces installed by the OLM installer. (Available through crwctl, the OLM installer uses the Operator Lifecycle Manager to install CodeReady Workspaces.)

10.5. 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 CodeReady Workspaces installed by the OLM installer:

Prerequisites

  • CodeReady Workspaces is installed by the OLM installer.

Procedure

  1. Find the CodeReady Workspaces Operator subscription name:

    $ oc get subscriptions -n openshift-workspaces
    Copy to Clipboard Toggle word wrap
  2. Get the CSV (Cluster Service Version) name from the CodeReady Workspaces Operator subscription:

    $ oc get subscription <subscription-name> -n openshift-workspaces -o yaml | grep installedCSV
    Copy to Clipboard Toggle word wrap
  3. Edit the ClusterServiceVersion YAML manifest:

    $ oc edit csv <csv-name> -n openshift-workspaces
    Copy to Clipboard Toggle word wrap
  4. Add the following environment variable to the Operator Deployment spec:

     - name: ADD_COMPONENT_READINESS_INIT_CONTAINERS
       value: "true"
    Copy to Clipboard Toggle word wrap
  5. Wait for the CodeReady Workspaces Operator restart to finish. The restarted Operator will then continue with restarting some of its components.
Note

Repeat these steps after each CodeReady Workspaces upgrade when a new CSV is created by OLM.

10.6. Disabling the readiness init containers for the OLM installer

To disable the previously enabled readiness init containers for the CodeReady Workspaces installed by the OLM installer:

Prerequisites

  • CodeReady Workspaces is installed by the OLM installer.

Procedure

  1. Find the CodeReady Workspaces Operator subscription name:

    $ oc get subscriptions -n openshift-workspaces
    Copy to Clipboard Toggle word wrap
  2. Get the CSV (Cluster Service Version) name from the CodeReady Workspaces Operator subscription:

    $ oc get subscription <subscription-name> -n openshift-workspaces -o yaml | grep installedCSV
    Copy to Clipboard Toggle word wrap
  3. Edit the ClusterServiceVersion YAML manifest:

    $ oc edit csv <csv-name> -n openshift-workspaces
    Copy to Clipboard Toggle word wrap
  4. Remove the following environment variable from the Operator Deployment spec:

     - name: ADD_COMPONENT_READINESS_INIT_CONTAINERS
       value: "true"
    Copy to Clipboard Toggle word wrap
  5. Wait for the CodeReady Workspaces Operator restart to finish. The restarted Operator will then continue with restarting some of its components.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat