--- 格式版本: 2 标题: "Introducing autoscaling for Red Hat OpenShift on Oracle Cloud Infrastructure | cloud-infrastructure" 原文链接: "https://blogs.oracle.com/cloud-infrastructure/autoscaling-for-red-hat-openshift-on-oci" 发布日期: "2026-08-11" 发布时间校准状态: "found" 发布时间需复核: "否" 发布时间来源: "rule:local:strict_original_body" 发布时间证据: "August 11, 2026 3 minute read" 发布时间校准原因: "规则确认唯一严格发布时间，来源 local:strict_original_body" 发布时间校准置信度: "high" 发布时间候选数量: 5 发布时间严格候选数量: 1 发布时间原页读取状态: "source template page reused from URL open" 发布时间未找到原因: "" 发布时间校准时间: "2026-08-12T21:46:36+08:00" 发布时间仲裁状态: "skipped" 发布时间仲裁尝试次数: 0 发布时间仲裁耗时毫秒: 0 发现时间: "2026-08-12T21:43:00+08:00" 入库时间: "2026-08-12T13:46:36.795Z" 来源平台: "固定入口" 搜索渠道: "fixed_url" 搜索词: "https://blogs.oracle.com/?page=news" 匹配关键词: - "deployment" - "AI" 相关厂家: - "Oracle" 相关专家: [] 内容类型: "网页" 抓取工具: "CDP Render" 清洗工具: "CDP Text + Defuddle/Readability 正文提取" 原始附件: [] AI优质: "否" AI打分: 30 AI分档: "非优质" AI质检状态: "不通过" AI打分理由: "内容为OCI上OpenShift的通用自动扩缩容功能，不涉及超节点、AI Rack、机柜级AI系统或相关部件/供电/散热/互连等主题，与项目关注范围无关。" AI质检模型: "ali-deepseek-v4-flash" AI质检时间: "2026-08-12T21:47:15+08:00" AI主题相关性: 0 AI来源权威性: 15 AI新颖性: 5 AI技术细节: 0 AI商业部署信号: 0 AI完整性: 10 采集批次: "2026年8月12日20点58分23秒" 采集批次ID: "20260812-205823-234" 去重键: "https://blogs.oracle.com/cloud-infrastructure/autoscaling-for-red-hat-openshift-on-oci" --- Oracle and Red Hat continue to expand Red Hat OpenShift on Oracle Cloud Infrastructure (OCI), helping you run enterprise Kubernetes workloads with more automation, flexibility, and operational consistency. Today, Oracle and Red Hat are introducing autoscaling support for OpenShift on OCI, generally available for OpenShift 4.22 and later. Your clusters can now adjust worker capacity automatically as application demand changes, so you can run dynamic workloads without manually resizing worker pools. You can enable elastic worker capacity when you create a new OpenShift cluster on OCI, or add it to a cluster you already run. ## Why autoscaling matters Application demand is rarely static. Development environments, batch processing, data services, AI workloads, and seasonal business applications all shift compute demand throughout the day. Without autoscaling, you either size worker capacity for peak demand or add nodes by hand when workloads cannot be scheduled. Both increase operational effort, and the first leaves compute resources idle during quieter periods. Autoscaling on OCI expands worker capacity when more compute is needed and contracts it when demand drops, within the limits you define. ## How this works with OpenShift autoscaling Autoscaling for OpenShift on OCI drives the standard OpenShift autoscaling machinery rather than replacing it, and operates alongside the autoscaling controls you already use. When pods cannot be scheduled, the cluster autoscaler increases the replica count on the relevant machine deployment. Cluster API creates the corresponding machine and machine set resources, and the Cluster API Provider for OCI provisions the OCI compute instances behind them. You set the boundaries once, on an OCIClusterAutoscaler custom resource that carries minNodes and maxNodes, and the existing controllers do the rest. Nothing about your current autoscaling configuration has to change. If you already run the OpenShift cluster autoscaler or machine autoscalers, they continue to work as they do today. ## What you can do Autoscaling for OpenShift on OCI fits into the deployment experience you already use. You can: - Enable autoscaling when you create a cluster. - Add autoscaling to a cluster you already run. - Set minimum and maximum worker capacity. - Choose OCI virtual machine or bare-metal shapes for autoscaling workers. - Use OCI Object Storage as the source for the worker image. - Monitor scaling activity with the OpenShift resources you already use, including the OCIClusterAutoscaler status, machine deployments, machine sets and machines, node readiness, and controller logs. Autoscaling is integrated with the OpenShift on OCI Terraform stack, so you configure it alongside the existing cluster deployment and post-installation flows. ## Enabling autoscaling You can enable autoscaling in two ways. 1. **At install time.** Turn on autoscaling while you create a new OpenShift cluster on OCI. Use this when elastic worker capacity should be part of the cluster from the start. 2. **On an existing cluster.** Add autoscaling to an OpenShift cluster you already run on OCI, without rebuilding it. Both paths use the OpenShift on OCI Terraform stack to collect the required OCI and OpenShift configuration. ## Preparing the worker image Autoscaling workers use a Red Hat Enterprise Linux CoreOS (RHCOS) image that matches your OpenShift cluster version. Download the matching RHCOS image, upload it to OCI Object Storage, and give the Terraform stack a read-only pre-authenticated request (PAR) URL. For virtual machine workers, use the downloaded QCOW2 image directly. For bare-metal workers, prepare the image with iSCSI boot configuration before you upload it. Run the helper script in the OpenShift on OCI quickstart repository from a Linux host or virtual machine. ## Built for OpenShift operations on OCI Autoscaling builds on the operational model you already use for OpenShift clusters. You continue to use OpenShift tooling to inspect cluster state, workloads, nodes, and events, while OCI provides the underlying compute, networking, and image services. You keep a familiar operating experience and hand off the manual capacity management that workloads with changing demand would otherwise require. ## Availability and support Autoscaling for OpenShift on OCI is generally available and supported on OpenShift 4.22 and later. The autoscaling operator is fully supported by Oracle. Open support requests through Oracle Support. Red Hat support for your OpenShift subscription is unaffected and continues to apply to the cluster. ## Getting started 1. Choose the OpenShift cluster that needs autoscaling, or create a new one running OpenShift 4.22 or later. 2. Prepare the matching RHCOS worker image and upload it to OCI Object Storage. 3. Use the OpenShift on OCI Terraform stack to enable autoscaling, either at install time or on an existing cluster. 4. Configure the worker shape, image source, and minimum and maximum capacity. 5. Apply the stack and verify that the autoscaling resources are available in OpenShift. Detailed installation, validation, cleanup, and troubleshooting steps are in the project documentation.