5c159b050e
The agent-interactive-console and agent-interactive-console-serial@ services should have consistent Before/After edges since only one runs on each system (depending on whether there is a graphical console). Previously, set-hostname.service had a Before= dependency on agent-interactive-console.service only, which created an edge in the systemd diagrams from set-hostname to agent-interactive-console but not to agent-interactive-console-serial@. This fixes the inconsistency by: - Adding set-hostname.service to the After= directive in both console services - Removing the redundant Before= directive from set-hostname.service Both services now define the dependency consistently in the same direction. Assisted-by: Claude Code
OpenShift Installer
Supported Platforms
- AWS (Official Docs)
- Azure (Official Docs)
- Bare Metal (Official Docs)
- GCP (Official Docs)
- IBM Cloud (Official Docs)
- Nutanix (Official Docs)
- OpenStack (Official Docs)
- Power (Official Docs)
- Power VS (Official Docs)
- vSphere (Official Docs)
- z/VM (Official Docs)
Quick Start
First, install all build dependencies.
Clone this repository. Then build the openshift-install binary with:
hack/build.sh
This will create bin/openshift-install. This binary can then be invoked to create an OpenShift cluster, like so:
bin/openshift-install create cluster
The installer will show a series of prompts for user-specific information and use reasonable defaults for everything else.
In non-interactive contexts, prompts can be bypassed by providing an install-config.yaml.
If you have trouble, refer to the troubleshooting guide.
Connect to the cluster
Details for connecting to your new cluster are printed by the openshift-install binary upon completion, and are also available in the .openshift_install.log file.
Example output:
INFO Waiting 10m0s for the openshift-console route to be created...
INFO Install complete!
INFO To access the cluster as the system:admin user when using 'oc', run
export KUBECONFIG=/path/to/installer/auth/kubeconfig
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.${CLUSTER_NAME}.${BASE_DOMAIN}:6443
INFO Login to the console with user: kubeadmin, password: 5char-5char-5char-5char
Cleanup
Destroy the cluster and release associated resources with:
openshift-install destroy cluster
Note that you almost certainly also want to clean up the installer state files too, including auth/, terraform.tfstate, etc.
The best thing to do is always pass the --dir argument to create and destroy.
And if you want to reinstall from scratch, rm -rf the asset directory beforehand.