Skip to content

Latest commit

 

History

History
46 lines (33 loc) · 2.28 KB

installation-on-kubernetes.md

File metadata and controls

46 lines (33 loc) · 2.28 KB
Raw

Deploying kube-opex-analytics on Kubernetes

Requirements

kube-opex-analytics requires read-only access to the following Kubernetes API endpoints.

  • /api/v1
  • /apis/metrics.k8s.io/v1beta1 (provided by Kubernetes Metrics Server, which shall be installed on the cluster if it's not yet the case).

On a typical deployment inside the Kubernetes cluster, the following Kubernetes API base URL shall be used: https://kubernetes.default.

Deployment manifests

kube-opex-analytics can be installed using one of the following methods:

Security Context: kube-opex-analytics's pod is deployed with a unprivileged security context by default. However, if needed, it's possible to launch the pod in privileged mode by setting the Helm configuration value securityContext.enabled to false.

Installation using kubectl and Kustomize

First review the default configuration settings in the deployment ConfigMap: kustomize/kube-opex-analytics-config.yaml.

Then, perform the following command to submit the deployment. The target namespace (kube-opex-analytics) is assumed to exist. Otherwise, create it first.

kubectl -n kube-opex-analytics apply -k ./manifests/kustomize

Installation using Helm

First review the default configuration settings in the Helm values file: manifests/helm/values.yaml. In particular, review the sections related to the persistent data volume, the Prometheus exporter and security context.

Then, perform the following command to submit the deployment. The target namespace (kube-opex-analytics) is assumed to exist. Otherwise, create it first.

helm upgrade -n kube-opex-analytics --install kube-opex-analytics manifests/helm/

Get Access to UI Service

The Helm deploys an HTTP service named kube-opex-analytics on port 80 in the selected namespace, providing to the built-in dashboard of kube-opex-analytics.