Install HO AWS

Installs the HyperShift Operator on AWS with external-dns and private platform settings.

538|560|Updated Jan 18, 2021
One-click install
npx skills add https://github.com/openshift/hypershift --skill install-ho-aws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Install HO AWS
Source: https://github.com/openshift/hypershift/tree/main/.claude/skills/dev/install-ho-aws
Command: npx skills add https://github.com/openshift/hypershift --skill install-ho-aws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up the HyperShift Operator on AWS requires a long, error-prone CLI command with many flags for external-dns, OIDC S3 storage, and private platform credentials. This Skill standardizes that installation so you can deploy the operator with a custom image and correct AWS configuration in one step.

Core Features & Use Cases

  • Custom Image Installation: Install the HyperShift Operator using any image tag from your container registry via the hypershift install command.
  • AWS Private Platform Support: Configures private AWS settings including region, credentials, and OIDC S3 bucket storage.
  • External-DNS Integration: Wires up external-dns with AWS provider credentials and a domain filter for hosted cluster DNS management.
  • Use Case: After building a custom HyperShift image with make build, install the operator into your management cluster with external-dns and OIDC configured for AWS-hosted control planes.

Quick Start

Source dev/claude-env.sh, then ask the assistant to install the HyperShift Operator using my custom image tag with AWS private and external-dns settings.

Frequently Asked Questions about Install HO AWS

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install the HyperShift Operator on AWS with a custom image?

Build the CLI with make hypershift, then run ./bin/hypershift install with --hypershift-image pointing to your custom image tag. Include flags for external-dns, OIDC S3 storage, and private AWS settings as shown in the command.

How to configure external-dns when installing HyperShift?

Pass --external-dns-provider=aws, --external-dns-credentials pointing to your AWS credentials file, and --external-dns-domain-filter with your domain. This lets the operator manage DNS records for hosted clusters automatically.

What environment variables are required before installing HyperShift Operator?

Source dev/claude-env.sh to set HO_IMAGE_REPO, AWS_CREDENTIALS, EXTERNAL_DNS_DOMAIN, OIDC_BUCKET, AWS_REGION, and MGMT_KUBECONFIG. These feed the install command's flags for registry, credentials, DNS, and OIDC configuration.

Do I need to rebuild the image after changing HyperShift CRD APIs?

No. Changes to CRD generated APIs only require running make api and make build, not a full image rebuild. You can then reinstall the operator with your existing image tag.

Why does hypershift install fail with credential errors?

The install fails if the AWS credentials file path is wrong or unreadable, or if MGMT_KUBECONFIG does not point to a reachable management cluster. Verify both files exist and the kubeconfig context is valid before running the command.