Eric Sauer

@pcarney8 @oybed @logandonley i believe we can close this out now that we have a katacoda tutorial, correct?

@dzungdo could this solution potentially replace some of the others in this directory? I looks like we have several different ways to automate the same activity, and i think it...

Some things i would like to see in this doc: * Ingress rules, limiting incoming traffic to traffic coming from router * Example of allowing traffic from another project/service to...

i think we could do most of this with a combination of a Scheduled job for docker-gc, and a set of scheduled jobs to run `oc adm prune` like: https://github.com/redhat-cop/openshift-management/tree/master/jobs#pruning-resources

Actually, that whole repo could probably get migrated into this one in some form. @sabre1041 what do you think?

I wanted to throw an alternative solution out there.... more and more, I am seeing value in trying to make applier as kubernetes-native as possible (i.e. making the openshift-specific bits...

We should also update the sample inventory in OpenShift Toolkit: https://github.com/redhat-cop/openshift-toolkit/tree/master/install

If nothing else, being able to specify a class on the anchor tags would be useful in enabling things like [Bootstrap Scrollspy](https://getbootstrap.com/docs/4.1/components/scrollspy/). The PR above appears to solve this and...

@raffaelespazzoli that makes sense. how do we want to proceed? @themoosman do you have time/desire to enhance your template to add MachineSets like @raffaelespazzoli's example?

@themoosman cool. Just so you know, we have standard variables already in place in automation for building out the MachineSets. take a look at https://github.com/redhat-cop/operationalizing-openshift-lab/blob/master/templates/machineautoscaler.yaml#L17-L23