Kubernetes
Last updated
Was this helpful?
Last updated
Was this helpful?
If you are running a K8S cluster, you can use fluent-bit to send data to Ascent. Please see below for instructions,
Ascent has provided its own fluent-bit daemon for deploying on K8S clusters. It is available at . It allows the administrator to pass a human-readable CLUSTER_ID
or cluster identifier with all the log data.
Providing a CLUSTER_ID allows Apica Ascent to separate namespaces that may be conflicting in two separate K8S clusters.
Clone the repository to get the kubectl
YAML files to start your daemonset
The files needed are under the folder fluent-bit
To get started run the following commands to create the namespace, service account and role setup:
The next step is to create a ConfigMap that will be used by the Fluent Bit DaemonSet:
You can enable TLS for Fluent Bit if you'd like to secure the data transferred through Fluent Bit to Apica Ascent. To do so, edit the `fluent-bit-config-logiq-forward.yaml` file as shown below.
Be sure to also configure the following:
name: LOGIQ_HOST value: "YOUR_LOGIQ_SERVER_IP"
name: LOGIQ_PORT value: "443"
name: CLUSTER_ID value: "YOUR_CLUSTER_ID"
name: LOGIQ_TOKEN value: "YOUR_INGEST_TOKEN"
name: LOGIQ_HOST
value: "YOUR_LOGIQ_SERVER_IP"
name: CLUSTER_ID
value: "YOUR_CLUSTER_ID"
name: LOGIQ_TOKEN
value: "YOUR_INGEST_TOKEN"
For Kubernetes version < 1.17, please change the apiVersion: "extensions/v1beta1" from "apps/v1" and remove selector attached to DaemonSet spec selector: matchLabels: k8s-app: fluent-bit-logging
Fluent Bit DaemonSet is ready to be used with Apica Ascent on a regular Kubernetes Cluster, configure the following in deamonset fluent-bit-daemonset-logiq-output.yml
. If you do not have your ingest token, You can generate them using