Skip to navigation
Skip to content
Featured links
지원
콘솔
개발자
평가판 시작
모든 Red Hat
고객용
고객 지원
서브스크립션 관리
기술문의 관리
Red Hat 에코시스템 카탈로그
파트너 검색
파트너용
파트너 포털
파트너 지원
파트너 되기
평가판, 구매 및 판매
Red Hat 스토어
영업팀에 문의
평가판 시작
Learning resources
교육 및 자격증
하이브리드 클라우드 학습 허브
인터렉티브 랩
학습 커뮤니티
Red Hat TV
아키텍처 센터
오픈 소스 커뮤니티
글로벌 지원
Red Hat 기여 방식
AI
학습
설명서
리소스
지원
콘솔
개발자
평가판 시작
연락처
언어 선택
English
Français
한국어
日本語
中文 (中国)
Deutsch
Italiano
Português
Español
홈
제품
OpenShift Container Platform
4.16
Operators
Chapter 4. Administrator tasks
Open
목차
Open page settings
OpenShift Container Platform
버전
4.22
4.21
4.20
4.19
4.18
4.17
4.16
4.15
4.14
4.13
4.12
4.11
4.10
4.9
4.8
4.7
4.6
4.5
4.4
4.3
4.2
4.1
3.11
3.10
3.9
3.7
3.6
3.5
3.4
3.3
3.2
3.1
3.0
2
이 문서는 모든 버전에서 사용 가능하지 않을 수 있습니다.
모든 버전의 제품 페이지 보기
형식
멀티 페이지
단일 페이지
모든 문서를 PDF로 표시
4.1. Adding Operators to a cluster
4.1.1. About Operator installation with OperatorHub
4.1.2. Installing from OperatorHub by using the web console
4.1.3. Installing from OperatorHub by using the CLI
4.1.4. Preparing for multiple instances of an Operator for multitenant clusters
4.1.5. Installing global Operators in custom namespaces
4.1.6. Pod placement of Operator workloads
4.1.7. Controlling where an Operator is installed
4.2. Updating installed Operators
4.2.1. Preparing for an Operator update
4.2.2. Changing the update channel for an Operator
4.2.3. Manually approving a pending Operator update
4.2.4. Additional resources
4.3. Deleting Operators from a cluster
4.3.1. Deleting Operators from a cluster using the web console
4.3.2. Deleting Operators from a cluster using the CLI
4.3.3. Refreshing failing subscriptions
4.4. Configuring Operator Lifecycle Manager features
4.4.1. Disabling copied CSVs
4.5. Configuring proxy support in Operator Lifecycle Manager
4.5.1. Overriding proxy settings of an Operator
4.5.2. Injecting a custom CA certificate
4.5.3. Additional resources
4.6. Viewing Operator status
4.6.1. Operator subscription condition types
4.6.2. Viewing Operator subscription status by using the CLI
4.6.3. Viewing Operator catalog source status by using the CLI
4.7. Managing Operator conditions
4.7.1. Overriding Operator conditions
4.7.2. Updating your Operator to use Operator conditions
4.7.3. Additional resources
4.8. Allowing non-cluster administrators to install Operators
4.8.1. Understanding Operator installation policy
4.8.2. Scoping Operator installations
4.8.3. Operator catalog access control
4.8.4. Troubleshooting permission failures
4.9. Managing custom catalogs
4.9.1. Prerequisites
4.9.2. File-based catalogs
4.9.3. SQLite-based catalogs
4.9.4. Catalog sources and pod security admission
4.9.5. Adding a catalog source to a cluster
4.9.6. Accessing images for Operators from private registries
4.9.7. Disabling the default OperatorHub catalog sources
4.9.8. Removing custom catalogs
4.10. Using Operator Lifecycle Manager on restricted networks
4.10.1. Prerequisites
4.10.2. Disabling the default OperatorHub catalog sources
4.10.3. Mirroring an Operator catalog
4.10.4. Adding a catalog source to a cluster
4.10.5. Next steps
4.11. Catalog source pod scheduling
4.11.1. Disabling default CatalogSource objects at a local level
4.11.2. Overriding the node selector for catalog source pods
4.11.3. Overriding the priority class name for catalog source pods
4.11.4. Overriding tolerations for catalog source pods
4.12. Troubleshooting Operator issues
4.12.1. Operator subscription condition types
4.12.2. Viewing Operator subscription status by using the CLI
4.12.3. Viewing Operator catalog source status by using the CLI
4.12.4. Querying Operator pod status
4.12.5. Gathering Operator logs
4.12.6. Disabling the Machine Config Operator from automatically rebooting
4.12.7. Refreshing failing subscriptions
4.12.8. Reinstalling Operators after failed uninstallation