logiq-repo. Whenever you install charts from this repository, ensure that you use the repository name as the prefix in your install command, as shown below.
logiq. You can also name your namespace differently by replacing
logiqwith the name of your choice in the command above. In case you do, remember to use the same namespace for the rest of the instructions listed in this guide.
values.yamlfiles for small, medium, and large clusters. You can use these files as a base for configuring your LOGIQ deployment. You can download these files from the following links.
values.yamlfile with the
helm installcommand using the
-fflag, as shown in the following example.
values.yamlfile you used during deployment, you can log into the LOGIQ PaaS UI using the following default credentials.
https://logiq.my-domain.comthat you set in the ingress controller service.
AWS_SECRET_ACCESS_KEYand name your S3 bucket uniquely.
cloudProviderthat is hosting the S3 compatible bucket. Currently, only
logiq-certs.yaml. You can now install the LOGIQ Helm chart, along with the certificates using the following command.
StorageClassnames and their default provisioner for each cloud provider.
falseif an external Postgres cluster is being used
logiqctl, generate an API token from the LOGIQ UI, as shown in the following image.
falseif you're using an external Redis cluster.
cluster_idof your choice while running the following install command. This helps you identify your LOGIQ cluster in case you'd like to monitor it.
values.yaml, as shown in the following example.
NodePortand pass the service types in the install command, as shown in the following example.
logiq.ai/nodeto control the placement of ingest pods for log data into ingest-optimised nodes, thereby allowing you to manage costs and instance sizing effectively.
values.yamlfile. In the following example, different node pools such as
3000on the ingress controller. The deployed Grafana instance uses the same login credentials as the LOGIQ UI.