b241c4e115
* pkg/asset/manifests: add MCO operator manifest Adds manifest generation for MCO configuration. Currently the manifest is only generated when custom boot images are specified, in order to disable MCO management of those boot images. The manifest generation uses a golang template as testing revealed that API server validation would not permit the manifests generated from serializing the golang structs, which would be more consistent with how we generate manifests for other openshift operators. As golang will populate the zero value for any non-pointer struct this triggered validation, where the API server expected certain required fields for these zero-value structs. Using a template allows us to bypass this problem. Fixes OCPBUGS-57348 * fixup! pkg/asset/manifests: add MCO operator manifest * fixup! pkg/asset/manifests: add MCO operator manifest
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.