The Administration section covers instance-level configuration of Deckhouse Code: access control, authentication, security, monitoring, maintenance mode, backup, and upgrade.
Pages that differ by installation type
Deckhouse Code is delivered as a Linux package, Omnibus Docker, a Helm Chart, or a Deckhouse Kubernetes Platform module. In Monitoring and limits the built-in monitoring of each installation type is a tab. Backup and restore and Upgrade are single pages: the part shared by every installation type comes first, and each step whose command differs is a tab per type. Relay (KAS) is enabled, addressed and checked differently on the Linux package, in Omnibus Docker and in the Helm Chart, and each of these steps is a tab per type.
Other pages
- License — viewing, installing and removing the license key of the instance.
- Users and access — restricting who can create groups and projects, and instance-wide access controls.
- Authentication — configuring sign-in through OmniAuth providers and LDAP.
- Security settings — instance-wide security settings, including sign-up restrictions and administrator two-factor authentication.
- Security credentials — reviewing and revoking tokens, SSH keys, and GPG keys issued across the instance.
- Service accounts — creating service accounts for CI/CD pipelines and integrations.
- Audit events — viewing the audit events recorded for the instance.
- Maintenance mode — reducing write operations during maintenance tasks.
- Advanced search — operating full-text search indexing after OpenSearch is connected.
- Runners — the runner images and example deployments with autoscaling on Deckhouse Virtualization Platform, the Docker executor and the Kubernetes executor.
Cluster-level operations of the Deckhouse Kubernetes Platform module — sizing, network configuration, migration from the Linux package or Omnibus Docker to the module and back — are described in the module documentation.