I've got origin 3.9 running and trying to setup an admission controller
webhook. I added the appropriate confgurations to master-config.yaml. I
added the following:
kind: ValidatingWebhookConfiguration
apiVersion: admissionregistration.k8s.io/v1beta1
metadata:
name: opa-validating-webhook
webh
Hello,
It's time for our weekly PaaS SIG sync-up meeting
Time: 1700 UTC - Wednesdays (date -d "1700 UTC")
Date: Tomorrow Wednesday, 25 July 2018
Where: IRC- Freenode - #centos-devel
Agenda:
- OpenShift Current Status
-- rpms
-- automation
- Open Floor
Minutes from last meeting:
https://www.cent
Thanks,
Is it possible to also do that with masters post upgrade? Do you have any
info you could point me at to create the new node groups post upgrade?
On Tue, Jul 24, 2018 at 3:00 PM Clayton Coleman wrote:
> Upgrading from regular nodes to autoscaling groups is not implemented.
> You’d have
Upgrading from regular nodes to autoscaling groups is not implemented.
You’d have to add new node groups post upgrade and manage it that way.
> On Jul 24, 2018, at 7:22 AM, David Conde wrote:
>
> I'm in the process of upgrading an origin cluster running on AWS from 3.7 to
> 3.9 using openshift a
I'm in the process of upgrading an origin cluster running on AWS from 3.7
to 3.9 using openshift ansible. I'd like the new instances to be registered
in autoscaling groups.
I have seen that if I create a new origin 3.9 cluster using the AWS
playbooks this happens as part of the install, how would
