git clone [email protected]:banzaicloud/logging-operator.git
cd logging-operator
kubectl create ns logging
kubectl -n logging create -f ./docs/deploy/manifests/rbac.yaml
kubectl -n logging create -f ./config/crd/bases/logging.banzaicloud.io_clusterflows.yaml
kubectl -n logging create -f ./config/crd/bases/logging.banzaicloud.io_clusteroutputs.yaml
kubectl -n logging create -f ./config/crd/bases/logging.banzaicloud.io_flows.yaml
kubectl -n logging create -f ./config/crd/bases/logging.banzaicloud.io_loggings.yaml
kubectl -n logging create -f ./config/crd/bases/logging.banzaicloud.io_outputs.yaml
kubectl -n logging create -f ./docs/deploy/manifests/deployment.yaml
helm repo add banzaicloud-stable https://kubernetes-charts.banzaicloud.com
helm repo update
helm install --namespace logging --name logging banzaicloud-stable/logging-operator
You can install
logging
resource via Helm chart with built-in TLS generation.
$ kubectl -n logging get pods
NAME READY STATUS RESTARTS AGE
logging-logging-operator-599c9cf846-5nw2n 1/1 Running 0 52s
$ kubectl get crd
NAME CREATED AT
clusterflows.logging.banzaicloud.io 2019-11-01T21:30:18Z
clusteroutputs.logging.banzaicloud.io 2019-11-01T21:30:18Z
flows.logging.banzaicloud.io 2019-11-01T21:30:18Z
loggings.logging.banzaicloud.io 2019-11-01T21:30:18Z
outputs.logging.banzaicloud.io 2019-11-01T21:30:18Z