- Logging operator requires Kubernetes v1.14.x or later.
- For the Helm base installation you need Helm v2.16.0 or later.
Complete the following steps to deploy the Logging operator using Kubernetes manifests. Alternatively, you can also install the operator using Helm.
- Clone the logging-operator repo.
git clone [email protected]:banzaicloud/logging-operator.git
- Navigate to the
logging-operator
folder.cd logging-operator
- Create a controlNamespace called “logging”.
kubectl create ns logging
- Create a ServiceAccount and install cluster roles.
kubectl -n logging create -f ./docs/deploy/manifests/rbac.yaml
- Apply the ClusterResources.
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
- Deploy the Logging operator.
kubectl -n logging create -f ./docs/deploy/manifests/deployment.yaml
Complete the following steps to deploy the Logging operator using Helm. Alternatively, you can also install the operator using Kubernetes manifests.
Note: For the Helm base installation you need Helm v2.16.0 or later.
- Add operator chart repository.
helm repo add banzaicloud-stable https://kubernetes-charts.banzaicloud.com helm repo update
- Install the Logging Operator
- Helm v2
helm install --namespace logging --name logging banzaicloud-stable/logging-operator
- Helm v3
kubectl create ns logging helm install --namespace logging logging banzaicloud-stable/logging-operator --set createCustomResource=false
You can install the
logging
resource with built-in TLS generation using a Helm chart.
To verify that the installation was successful, complete the following steps.
- Check the status of the pods. You should see a new logging-operator pod.
$ kubectl -n logging get pods NAME READY STATUS RESTARTS AGE logging-logging-operator-599c9cf846-5nw2n 1/1 Running 0 52s
- Check the CRDs. You should see the following five new CRDs.
$ 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