...
Above configuration is good enough to get started. However, for more advanced/production grade customizations please ensure to review the prerequisites for advanced use cases page.
Installation
Kloudfuse follows standard helm best practices. Please follow these steps to install the Kloudfuse stack.
Step 1. Login to Kloudfuse helm registry using the “
single-node-install-token.json" provided in your email. (see here if following command fails). If you do not have this token or haven’t received the email, please contact us.
| Code Block |
|---|
cat single-node-install-token.json | helm registry login -u _json_key --password-stdin https://us-east1-docker.pkg.dev |
...
| Code Block |
|---|
helm upgrade --install -n kfuse kfuse oci://us-east1-docker.pkg.dev/mvp-demo-301906/kfuse-helm/kfuse --version 2.7.0-rc2 -f custom_values.yaml |
UI
Upon completion of the above helm install you would see instructions for accessing the Kloudfuse Platform UI.
...
Please follow the steps here to configure Google Auth or change the default password.
Please see next steps to explore more.
...
The standard Kloudfuse install sends its telemetry data to itself as well as the Kloudfuse cloud (observe.kloudfuse.io). This is so that we can monitor the health of the installed Kloudfuse stack(s) across our customers and help resolve any issues quickly. If you wish to disable sending telemetry data to Kloudfuse cloud, please contact us .
Next
Please see Migration scenarios & integrations to understand and choose what suits your need.
...