hypershift:cluster

You can create ephemeral OpenShift clusters on AWS by orchestrating HyperShift to provision resources with custom worker node configurations, instance types, and OCP versions. This simplifies spinning up temporary clusters for testing Kagenti in real Kubernetes environments.

Yes, you can customize worker node instance types, replica counts, and OpenShift versions during cluster provisioning. The orchestration supports custom configurations to match your specific testing requirements for Kagenti deployments.

Managing the lifecycle of temporary HyperShift clusters involves orchestrating both creation and destruction processes. This approach handles AWS resource provisioning and teardown reliably, ensuring efficient management of temporary OpenShift testing environments.

You can destroy OpenShift clusters on AWS using the cluster teardown functionality. Reliably destroying created clusters ensures efficient AWS resource management by removing temporary infrastructure after testing Kagenti deployments is complete.

Yes, you need AWS resources configured before provisioning HyperShift clusters. The cluster provisioning process integrates directly with AWS for resource allocation and management, requiring proper cloud infrastructure access to create and destroy OpenShift environments.

Using ephemeral OpenShift clusters avoids manual cloud infrastructure management during testing. You can quickly create a cluster, deploy Kagenti, run tests, and destroy the cluster, ensuring clean environments without persistent AWS resource overhead.