mirror of
https://github.com/openshift/installer.git
synced 2026-02-05 06:46:36 +01:00
d9d6e4bd80
Folks are free to opt-in to the machine API during a UPI flow, but creating Machine(Set)s that match their host environment requires matching a few properties (subnet, securityGroups, ...). Our default templates are unlikely to do that out of the box, so just remove them with the standard flow. Users who want to wade in can do so, and I've adjusted our CloudFormation templates to set the same tags as our IPI assets to make this easier. But with the rm call, other folks don't have to worry about broken Machine(Set)s in their cluster confusing the machine API or other admins. The awkward join syntax for subnet names is because YAML doesn't support nesting !s [1]: You can't nest short form functions consecutively, so a pattern like !GetAZs !Ref is invalid. Also fix a few unrelated nits, e.g. the unused VpcId property in 06_cluster_worker_node.yaml. [1]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-getavailabilityzones.html#w2ab1c21c24c36c17b8
AWS Account Set Up
This document is a guide for preparing a new AWS account for use with OpenShift. It will help prepare an account to create a single cluster and provide insight for adjustments which may be needed for additional clusters.
Follow along with the steps and links below to configure your AWS account and provision an OpenShift cluster:
Reporting Issues
Please see the Issue Tracker for current known issues. Please report a new issue if you do not find an issue related to any trouble you're having.