> Oh wow, I figured we’d have to blow away the cluster to get the scaling
groups. Was most of the work on the masters? Because I presume you just
deleted the 3.6 nodes and recreated them in the scaling group?
The masters were ok (they are the only nodes not in a scaling group at the
moment),
.@agiledigital.com.au> wrote:
>>
>>> Have you seen the AWS reference architecture?
>>> https://access.redhat.com/documentation/en-us/reference_architectures/2018/html/deploying_and_managing_openshift_3.9_on_amazon_web_services/index#
>>> On Tue, 2 Oct 2018 at 3:11
ference architecture?
>> https://access.redhat.com/documentation/en-us/reference_architectures/2018/html/deploying_and_managing_openshift_3.9_on_amazon_web_services/index#
>> On Tue, 2 Oct 2018 at 3:11 am, Peter Heitman wrote:
>>
>>> I've created a CloudFormation Stack for simple lab
ple lab-test deployments of
> OpenShift Origin on AWS. Now I'd like to understand what would be best for
> production deployments of OpenShift Origin on AWS. In particular I'd like
> to create the corresponding CloudFormation Stack.
>
> I've seen the Install Guide page on Configurin
I've created a CloudFormation Stack for simple lab-test deployments of
OpenShift Origin on AWS. Now I'd like to understand what would be best for
production deployments of OpenShift Origin on AWS. In particular I'd like
to create the corresponding CloudFormation Stack.
I've seen the Install Guide
If you ever want to run containers on the master (which btw is fine),
you'll want that dedicated volume. I suggest you set it up that way out of
the gate to avoid hassles.
If you don't, you end up with the loop-lvm driver which tends to be slower
than others (might be OK for your case).
Here is
