Skip to navigation
Skip to content
Featured links
支持
控制台（Console）
开发人员
开始试用
所有红帽
对于客户
客户支持
订阅管理
支持问题单
红帽生态系统目录
查找合作伙伴
对于合作伙伴
合作伙伴门户
合作伙伴支持
成为一个合作伙伴
尝试、购买和销售
红帽商店
联系销售人员
开始试用
Learning resources
培训和认证
混合云学习中心
互动实验室
学习社区
Red Hat TV
架构中心
开源社区
全球倡导
我们贡献的方式
AI
学习
文档
资源
支持
控制台（Console）
开发人员
开始试用
联系人
选择语言
English
Français
한국어
日本語
中文 (中国)
Deutsch
Italiano
Português
Español
主页
产品
OpenShift Container Platform
4.14
Scalability and performance
Chapter 22. Clusters at the network far edge
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 文档
22.1. Challenges of the network far edge
22.1.1. Overcoming the challenges of the network far edge
22.1.2. Using GitOps ZTP to provision clusters at the network far edge
22.1.3. Installing managed clusters with SiteConfig resources and RHACM
22.1.4. Configuring managed clusters with policies and PolicyGenTemplate resources
22.2. Preparing the hub cluster for ZTP
22.2.1. Telco RAN DU 4.14 validated software components
22.2.2. Recommended hub cluster specifications and managed cluster limits for GitOps ZTP
22.2.3. Installing GitOps ZTP in a disconnected environment
22.2.4. Adding RHCOS ISO and RootFS images to the disconnected mirror host
22.2.5. Enabling the assisted service
22.2.6. Configuring the hub cluster to use a disconnected mirror registry
22.2.7. Configuring the hub cluster to use unauthenticated registries
22.2.8. Configuring the hub cluster with ArgoCD
22.2.9. Preparing the GitOps ZTP site configuration repository
22.3. Updating GitOps ZTP
22.3.1. Overview of the GitOps ZTP update process
22.3.2. Preparing for the upgrade
22.3.3. Labeling the existing clusters
22.3.4. Stopping the existing GitOps ZTP applications
22.3.5. Required changes to the Git repository
22.3.6. Installing the new GitOps ZTP applications
22.3.7. Rolling out the GitOps ZTP configuration changes
22.4. Installing managed clusters with RHACM and SiteConfig resources
22.4.1. GitOps ZTP and Topology Aware Lifecycle Manager
22.4.2. Overview of deploying managed clusters with GitOps ZTP
22.4.3. Creating the managed bare-metal host secrets
22.4.4. Configuring Discovery ISO kernel arguments for installations using GitOps ZTP
22.4.5. Deploying a managed cluster with SiteConfig and GitOps ZTP
22.4.6. Monitoring managed cluster installation progress
22.4.7. Troubleshooting GitOps ZTP by validating the installation CRs
22.4.8. Troubleshooting GitOps ZTP virtual media booting on Supermicro servers
22.4.9. Removing a managed cluster site from the GitOps ZTP pipeline
22.4.10. Removing obsolete content from the GitOps ZTP pipeline
22.4.11. Tearing down the GitOps ZTP pipeline
22.5. Configuring managed clusters with policies and PolicyGenTemplate resources
22.5.1. About the PolicyGenTemplate CRD
22.5.2. Recommendations when customizing PolicyGenTemplate CRs
22.5.3. PolicyGenTemplate CRs for RAN deployments
22.5.4. Customizing a managed cluster with PolicyGenTemplate CRs
22.5.5. Monitoring managed cluster policy deployment progress
22.5.6. Validating the generation of configuration policy CRs
22.5.7. Restarting policy reconciliation
22.5.8. Changing applied managed cluster CRs using policies
22.5.9. Indication of done for GitOps ZTP installations
22.6. Manually installing a single-node OpenShift cluster with ZTP
22.6.1. Generating GitOps ZTP installation and configuration CRs manually
22.6.2. Creating the managed bare-metal host secrets
22.6.3. Configuring Discovery ISO kernel arguments for manual installations using GitOps ZTP
22.6.4. Installing a single managed cluster
22.6.5. Monitoring the managed cluster installation status
22.6.6. Troubleshooting the managed cluster
22.6.7. RHACM generated cluster installation CRs reference
22.7. Recommended single-node OpenShift cluster configuration for vDU application workloads
22.7.1. Running low latency applications on OpenShift Container Platform
22.7.2. Recommended cluster host requirements for vDU application workloads
22.7.3. Configuring host firmware for low latency and high performance
22.7.4. Connectivity prerequisites for managed cluster networks
22.7.5. Workload partitioning in single-node OpenShift with GitOps ZTP
22.7.6. Recommended cluster install manifests
22.7.7. Recommended postinstallation cluster configurations
22.8. Validating single-node OpenShift cluster tuning for vDU application workloads
22.8.1. Recommended firmware configuration for vDU cluster hosts
22.8.2. Recommended cluster configurations to run vDU applications
22.8.3. Checking that the recommended cluster configurations are applied
22.9. Advanced managed cluster configuration with SiteConfig resources
22.9.1. Customizing extra installation manifests in the GitOps ZTP pipeline
22.9.2. Filtering custom resources using SiteConfig filters
22.9.3. Deleting a node by using the SiteConfig CR
22.10. Advanced managed cluster configuration with PolicyGenTemplate resources
22.10.1. Deploying additional changes to clusters
22.10.2. Using PolicyGenTemplate CRs to override source CRs content
22.10.3. Adding custom content to the GitOps ZTP pipeline
22.10.4. Configuring policy compliance evaluation timeouts for PolicyGenTemplate CRs
22.10.5. Signalling GitOps ZTP cluster deployment completion with validator inform policies
22.10.6. Configuring power states using PolicyGenTemplates CRs
22.10.7. Configuring LVM Storage using PolicyGenTemplate CRs
22.10.8. Configuring PTP events with PolicyGenTemplate CRs
22.10.9. Configuring bare-metal events with PolicyGenTemplate CRs
22.10.10. Configuring the Image Registry Operator for local caching of images
22.10.11. Using hub templates in PolicyGenTemplate CRs
22.11. Updating managed clusters with the Topology Aware Lifecycle Manager
22.11.1. About the Topology Aware Lifecycle Manager configuration
22.11.2. About managed policies used with Topology Aware Lifecycle Manager
22.11.3. Installing the Topology Aware Lifecycle Manager by using the web console
22.11.4. Installing the Topology Aware Lifecycle Manager by using the CLI
22.11.5. About the ClusterGroupUpgrade CR
22.11.6. Update policies on managed clusters
22.11.7. Creating a backup of cluster resources before upgrade
22.11.8. Using the container image pre-cache feature
22.11.9. Troubleshooting the Topology Aware Lifecycle Manager
22.12. Updating managed clusters in a disconnected environment with the Topology Aware Lifecycle Manager
22.12.1. Updating clusters in a disconnected environment
22.12.2. About the auto-created ClusterGroupUpgrade CR for GitOps ZTP
22.13. Expanding single-node OpenShift clusters with GitOps ZTP
22.13.1. Applying profiles to the worker node
22.13.2. (Optional) Ensuring PTP and SR-IOV daemon selector compatibility
22.13.3. PTP and SR-IOV node selector compatibility
22.13.4. Using PolicyGenTemplate CRs to apply worker node policies to worker nodes
22.13.5. Adding worker nodes to single-node OpenShift clusters with GitOps ZTP
22.14. Pre-caching images for single-node OpenShift deployments
22.14.1. Getting the factory-precaching-cli tool
22.14.2. Booting from a live operating system image
22.14.3. Partitioning the disk
22.14.4. Downloading the images
22.14.5. Pre-caching images in GitOps ZTP
22.14.6. Troubleshooting