Allow non-HA deployment

[jbrannst]

FEATURE REQUEST INFO:

As a casual OCP user typically upgrading in a blue/green fashion I would like to run a non-HA setup in order to save AWS costs.

Problem Description

What problem is being solved by the proposed feature?
AWS is expensive by itself, I don't have HA requirements and should be able to save considerably by running 1 Master 1 Infra 2 AppNodes.

Proposed Change

Not sure what would need to change but we generate an inventory and can parametrize the number of app nodes. Something similar should be possible for master/infra nodes.
Add 2 new parameters,
master-node-count (default=3)
infra-node-count (default=3)

or perhaps just one parameter, as we anyway just want either 1 or 3 of each
ha-deployment (default=true)

Overview

Alternatives

Security Impact

Other End User Impact

Performance Impact

Other Deployer Impact

Developer Impact

Documentation Impact

Implementation

Describe your plan for implementation steps and potential
assignees/contributors.

Acceptance criteria

OCP deploys successfully on AWS in non-HA mode with 1 master, 1 Infra and 2 App nodes using your ose-on-aws wrapper script.

Testing

Describe how to test this, including manual steps, if any.

Dependencies

References

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale