1.8.3. Configuring the Service Mesh Operator to run on infrastructure nodes


This task should only be performed if the Service Mesh Operator runs on an infrastructure node.

If the operator will run on a worker node, skip this task.

Prerequisites

  • The Service Mesh Operator must be installed.
  • One of the nodes comprising the deployment must be an infrastructure node. For more information, see "Creating infrastructure machine sets."

Procedure

  1. List the operators installed in the namespace:

    $ oc -n openshift-operators get subscriptions
  2. Edit the Service Mesh Operator Subscription resource to specify where the operator should run:

    $ oc -n openshift-operators edit subscription <name> 
    1
    1
    <name> represents the name of the Subscription resource. The default name of the Subscription resource is servicemeshoperator.
  3. Add the nodeSelector and tolerations to spec.config in the Subscription resource:

    apiVersion: operators.coreos.com/v1alpha1
    kind: Subscription
    metadata:
      labels:
        operators.coreos.com/servicemeshoperator.openshift-operators: ""
      name: servicemeshoperator
      namespace: openshift-operators
    # ...
    spec:
      config:
        nodeSelector: 
    1
    
          node-role.kubernetes.io/infra: ""
        tolerations: 
    2
    
        - effect: NoSchedule
          key: node-role.kubernetes.io/infra
          value: reserved
        - effect: NoExecute
          key: node-role.kubernetes.io/infra
          value: reserved
    1
    Ensures that the operator pod is only scheduled on an infrastructure node.
    2
    Ensures that the pod is accepted by the infrastructure node.
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

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

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

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

Red Hat 문서 정보

Legal Notice

Theme

© 2026 Red Hat
맨 위로 이동