5.6. 修改集群

先决条件

• 您已刷新了 API 令牌。
• 您已将 CLUSTER_ID 导出为一个环境变量。

流程

• 运行以下命令来修改 Operator：

  $ curl https://api.openshift.com/api/assisted-install/v2/clusters/${CLUSTER_ID} \
  -X PATCH \
  -H "Authorization: Bearer ${API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '
  {
      "olm_operators": [{"name": "mce"}, {"name": "cnv"}], 

  1

  2

  
  }
  ' | jq '.id'

  Copy to Clipboard Toggle word wrap

  1

  为 OpenShift Virtualization 指定 cnv for OpenShift Virtualization, mtv for Migration Toolkit, mce for multicluster engine, odf for Red Hat OpenShift Data Foundation, lvm for Logical Volume Manager Storage, openshift-ai for OpenShift AI, osc for OpenShift 沙盒容器, nmstate for Kubernetes NMState, amd-gpu for AMD GPU, kmm for Kernel Module Management, node-feature-discovery for Node Feature Discovery, nvidia- gpu for NVIDIA GPU , self-node- remediation for Self Node Remediation , pipelines for OpenShift Pipelines , servicemesh for OpenShift Service Mesh , node- healthcheck for Node Health Check , lso for Local Storage Operator , fence-agents- remediation 用于 Fence Agents Remediation , kube- descheduler for Kube Descheduler , serverless for OpenShift Serverless , author ino for Authorino, Cluster Observability Operator 的 cluster - observability, metallb for MetalLB , numaresources for NUMA Resources , 和 oadp for OpenShift API for Data Protection。

  2

  要修改 Operator，请添加您要安装的 Operator 的新完整列表，而不只是区别。要删除所有 Operator，请指定空数组 ："olm_operators": []。

  输出示例

  {
    <various cluster properties>,
    "monitored_operators": [
      {
        "cluster_id": "b5259f97-be09-430e-b5eb-d78420ee509a",
        "name": "console",
        "operator_type": "builtin",
        "status_updated_at": "0001-01-01T00:00:00.000Z",
        "timeout_seconds": 3600
      },
      {
        "cluster_id": "b5259f97-be09-430e-b5eb-d78420ee509a",
        "name": "cvo",
        "operator_type": "builtin",
        "status_updated_at": "0001-01-01T00:00:00.000Z",
        "timeout_seconds": 3600
      },
      {
        "cluster_id": "b5259f97-be09-430e-b5eb-d78420ee509a",
        "name": "mce",
        "namespace": "multicluster-engine",
        "operator_type": "olm",
        "status_updated_at": "0001-01-01T00:00:00.000Z",
        "subscription_name": "multicluster-engine",
        "timeout_seconds": 3600
      },
      {
        "cluster_id": "b5259f97-be09-430e-b5eb-d78420ee509a",
        "name": "cnv",
        "namespace": "openshift-cnv",
        "operator_type": "olm",
        "status_updated_at": "0001-01-01T00:00:00.000Z",
        "subscription_name": "hco-operatorhub",
        "timeout_seconds": 3600
      },
      {
        "cluster_id": "b5259f97-be09-430e-b5eb-d78420ee509a",
        "name": "lvm",
        "namespace": "openshift-local-storage",
        "operator_type": "olm",
        "status_updated_at": "0001-01-01T00:00:00.000Z",
        "subscription_name": "local-storage-operator",
        "timeout_seconds": 4200
      }
    ],
    <more cluster properties>

  Copy to Clipboard Toggle word wrap

  注意

  输出是新集群状态的描述。输出中的 monitored_operators 属性包含两种类型的 Operator：

  • "operator_type": "builtin" ：此类型的 Operator 是 OpenShift Container Platform 不可分割的一部分。
  • "operator_type": "olm" ：此类型的 Operator 被用户手动或自动添加为一个依赖项。在本例中，LVM Storage Operator 被自动添加为 OpenShift Virtualization 的一个依赖项。

其他资源

• 如需了解您要安装的 Operator 及其前提条件和依赖项的概述，请参阅使用 Operator 和 Operator Bundles 自定义安装。