Prerequisites for advanced use cases

Please review following use cases which will require further customization on how the Kloudfuse stack is installed.

Installing Kloudfuse on a shared cluster

To understand more about installation on a shared cluster, please refer to the following.

Larger ingest volume of multiple streams.

At a minimum you will need a Kubernetes cluster with one node with 8 cores and 32 GB memory. For GCP, for example, you can use n2-standard-8 machine type. If you are planning to scale to higher volume you should use a 3 node cluster with machine type that has 16 cores and 128 GB of memory (n2-highmem-16 for GCP as an example). Ensure that the cpu platform chosen for the node groups is one of the newer platforms such as, “Intel Ice Lake”. Nodes with older cpu platforms (more common in GCP by default) can result in severe underperformance and should be strictly avoided.

Cloud storage for overflow and backup

For production clusters, Kloudfuse recommend using deepstore. However, if you do not wish to use deepstore, please contact the Kloudfuse team for a recommendation on such configuration.

For using the cloud storage you will need to configure cloud storage bucket or path in the same region as your Kubernetes cluster and provide the following configuration to the Kloudfuse installation (see https://kloudfuse.atlassian.net/wiki/spaces/EX/pages/724664352 for further details):

1. bucket path

2. secret key - only needed if the nodes in your Kubernetes cluster are not configured to have access to the bucket.

3. ability to provision persistent storage using Kubernetes storage classes. This requires AWS EBS CSI driver to be installed.

Kloudfuse Storage Encryption

Kloudfuse stack can use encrypted volumes for its storage. Learn more.

Setting up HTTPS/TLS

The Kfuse chart supports setting up HTTPS/TLS on the external ingress. Refer to https://kloudfuse.atlassian.net/wiki/spaces/EX/pages/789774337 for more details.

Setting up email notification for alerting

If you are going to use email based notifications for alerts, make sure to include email notifications settings as instructed.

Single Sign On (SSO) support

Kloudfuse platform supports oath2 based single sign on integration with various identity providers along with standalone accounts.

Changing default password for UI

To change the default password follow instructions here

Configuring relabel rules

Kloudfuse platform can be configured to rewrite labels of Metrics, Events, Logs, and Traces . Refer to https://kloudfuse.atlassian.net/wiki/spaces/EX/pages/803766284 for more details.

Configuring retention policies

Kloudfuse supports retention at the record-level. Refer to for more details.

Using Kfuse across different AWS accounts (or VPCs) using PrivateLink and VPC Service Endpoints

Kloudfuse can be configured to work across different accounts or VPCs within the same AWS cloud region. Refer to the steps here.

Managing Kloudfuse Alerts and Dashboards with Terraform

Any custom or component alerts or dashboards can be managed using terraform. Please follow instructions here.