The module lifecycle stage: General Availability

Available with limitations in:  CE, BE

Available without limitations in:  SE, SE+, EE

Web interface aims the simplicity of control and the transparency of a state of Deckhouse Kubernetes Platform.

All users have access to the interface according to their rights in the platform.

Assuming public domain template is %s.example.com, the web app will be available at https://console.example.com.

Overview

Features

  • Cluster overview, versions of Deckhouse and Kubernetes, the overall condition and updates
  • Deckhouse modules and their settings
  • Node management: configuration, scaling, and update settings
  • Multitenancy: projects and project templates
  • Access control: external authentication providers, group and user permissions
  • Ingress controllers to rul incoming traffic
  • Journaling: collecting logs from node file and pods, and sending them to various storage types
  • Monitoring: processing and sending of metrics, recording rules and alerts, Grafana dashboards and data sources, Prometheus settings, and a list of firing alerts
  • GitOps support: special marks on Kubernetes resources, created by automation like werf, Argo CD, Helm.
  • Metrics and monitoring dashboards in Nodegroups, Nodes, and Ingress Controllers
  • Pods of Prometheus, Ingress Controllers, and Nodes
  • And much more!

Turning on

The module must be turned on explicitly in ModuleConfig:

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
  name: console
spec:
  enabled: true

Resources requirements

Resources consumed by server-side pods are estimated as follows

Users CPU, cores RAM, MiB
0 0.02 80
1 0.04 100
10 0.37 120
100 0.85 260
1000 1.50 950

Vertical Pod Autoscaler is configured with a minimum CPU/memory limit of 100m/100MiB and a maximum of 1/512MiB. The server side pods are deployed in two replicas automatically for Deckhouse platform installation in HA mode.