32356ddc99
This allows users to feed in prexisting subnets. I've also added
classification logic copied from the upstream Kubernetes AWS cloud
provider for categorizing private vs. public subnets. There's no
explicit install-config field for the VPC; we'll extract that from the
given subnets.
populateSubnets is a bit heavy if all you need is the VPC, but Abhinav
prefers it [1], it would save future public/private subnet lookup by
warming those caches, and we'll only call Metadata.AWS late in
pkg/asset/cluster/tfvars.go (via a future commit), so the VPC
cache-warming logic doesn't get called at the moment anyway.
There's no verification yet; we'll get to that in follow-up work.
More on the DescribeSubnetsPagesWithContext FIXME in 37a7f49c77
(pkg/destroy/aws: Delete subnets by VPC, 2019-08-13, #2214).
[1]: https://github.com/openshift/installer/pull/2477#discussion_r334701272
OpenShift Installer
Supported Platforms
- AWS
- AWS (UPI)
- Azure
- Bare Metal (UPI)
- Bare Metal (IPI) (Experimental)
- GCP
- GCP (UPI)
- Libvirt with KVM (development only)
- OpenStack (experimental)
- vSphere
Quick Start
First, install all build dependencies.
Clone this repository to src/github.com/openshift/installer in your GOPATH. 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 install and destroy.
And if you want to reinstall from scratch, rm -rf the asset directory beforehand.