Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

Chapter 13. Provisioning virtual machines on OpenShift Virtualization

OpenShift Virtualization addresses the needs of development teams that have adopted or want to adopt Red Hat OpenShift Container Platform but possess existing virtual machine (VM) workloads that cannot be easily containerized. This technology provides a unified development platform where developers can build, modify, and deploy applications residing in application containers and VMs in a shared environment. These capabilities support rapid application modernization across the open hybrid cloud.

You can create a compute resource for OpenShift Virtualization so that you can provision and manage virtual machines in OpenShift Container Platform by using Satellite.

Note that template provisioning is not supported for this release.

Important

The OpenShift Virtualization compute resource is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

Prerequisites

  • You can use synchronized content repositories for Red Hat Enterprise Linux. For more information, see Synchronizing repositories in Managing content.
  • Provide an activation key for host registration. For more information, see Creating an activation key in Managing content.
  • You must have cluster-admin permissions for the OpenShift Container Platform cluster.
  • A Capsule Server managing a network on the OpenShift Container Platform cluster. Ensure that no other DHCP services run on this network to avoid conflicts with Capsule Server. For more information about network service configuration for Capsule Servers, see Preparing networking in Provisioning hosts.
  • Ensure the provisioning user has the required permissions to provision hosts. For more information, see Appendix D, Permissions required to provision hosts.
Warning

By default, deleting a host entry associated with a virtual machine does not destroy the virtual machine on the compute resource.

To change the default behavior, navigate to Administer > Settings > Provisioning and set Destroy associated VM on host delete to Yes.

13.1. Adding an OpenShift Virtualization connection to Satellite Server
リンクのコピー

Use this procedure to add OpenShift Virtualization as a compute resource in Satellite.

Procedure

  1. Enter the following satellite-installer command to enable the OpenShift Virtualization plugin for Satellite: 

    # satellite-installer --enable-foreman-plugin-kubevirt
    Copy to Clipboard Toggle word wrap

  2. Obtain a token to use for HTTP and HTTPs authentication:

    1. Log in to the OpenShift Container Platform cluster and list the secrets that contain tokens: 

      $ oc get secrets
      Copy to Clipboard Toggle word wrap

    2. Obtain the token for your secret: 

      $ oc get secrets MY_SECRET -o jsonpath='{.data.token}' | base64 -d | xargs
      Copy to Clipboard Toggle word wrap
    3. Record the token to use later in this procedure.
  3. In the Satellite web UI, navigate to Infrastructure > Compute Resources, and click Create Compute Resource.
  4. In the Name field, enter a name for the new compute resource.
  5. From the Provider list, select OpenShift Virtualization.
  6. In the Description field, enter a description for the compute resource.
  7. In the Hostname field, enter the FQDN, hostname, or IP address of the OpenShift Container Platform cluster.
  8. In the API Port field, enter the port number that you want to use for provisioning requests from Satellite to OpenShift Virtualization.
  9. In the Namespace field, enter the user name of the OpenShift Container Platform cluster.
  10. In the Token field, enter the bearer token for HTTP and HTTPs authentication.
  11. Optional: In the X509 Certification Authorities field, enter a certificate to enable client certificate authentication for API server calls.
トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat