Skip to content
This repository was archived by the owner on Jan 25, 2022. It is now read-only.

Conversation

@themoosman
Copy link
Contributor

Add template to install EFK stack on OCP 4.1.

Fully tested on a 4.1.8 cluster.

Resolves issue #5

@themoosman
Copy link
Contributor Author

Template construction based off this OCP documentation. https://docs.openshift.com/container-platform/4.1/logging/efk-logging-deploying.html

@etsauer etsauer added the enhancement New feature or request label Aug 6, 2019
@raffaelespazzoli
Copy link

I was working on a similar template. I think the logging stack should probably run on separate nodes. Using taints and toleration we should make sure only the logging stack ends up on those nodes. This would work similarly to how masters are kept isolated for normal workloads.
here is my recipe: https://github.com/raffaelespazzoli/openshift-enablement-exam/tree/master/misc4.0/logging

@etsauer
Copy link
Collaborator

etsauer commented Aug 6, 2019

@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
Copy link
Contributor Author

Sure, I can probably get to it in the next week or so. @etsauer

@etsauer
Copy link
Collaborator

etsauer commented Aug 6, 2019

@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

@themoosman
Copy link
Contributor Author

Added support for node selectors. I made this very generic as to work with the OOTB cluster as well as any custom MachineSets.

Copy link
Collaborator

@etsauer etsauer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@themoosman when I try to run this, I get an error on one of the resources:

$ oc process -f templates/install-efk.yaml | oc apply -f -
namespace/openshift-logging created
namespace/openshift-operators-redhat created
operatorgroup.operators.coreos.com/openshift-operators-redhat created
operatorgroup.operators.coreos.com/openshift-logging-ogog created
catalogsourceconfig.operators.coreos.com/elasticsearch created
catalogsourceconfig.operators.coreos.com/installed-community-openshift-logging created
subscription.operators.coreos.com/elasticsearch-operator created
role.rbac.authorization.k8s.io/prometheus-k8s created
rolebinding.rbac.authorization.k8s.io/prometheus-k8s created
subscription.operators.coreos.com/cluster-logging created
error: unable to recognize no matches for kind "ClusterLogging" in version "logging.openshift.io/v1"

@themoosman
Copy link
Contributor Author

Circling back on this. Where did we land on splitting this into 2 templates?

@etsauer
Copy link
Collaborator

etsauer commented Aug 28, 2019

@themoosman I think we agreed that split into two is better.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants