Deckhouse Stronghold in Yandex Cloud

Everything is installed, configured, and working

Below are the Deckhouse Stronghold capabilities available right after installation.

By default, all components are accessed through Dex using the static user created in the cluster during installation.

Here are credentials generated in the previous steps:

  • Username — admin@deckhouse.io
  • Password — <GENERATED_PASSWORD> (you can also find it in the User in the config.yml file)

Open https://stronghold.example.com in your browser and sign in via Dex using the provided username and password.

Getting started with the cluster

📚 Documentation

Documentation for the Deckhouse Platform version installed in your cluster.

Web service name: documentation

📊 Monitoring

Explore Grafana dashboards bundled with Deckhouse Platform.

Web service name: grafana

To access Prometheus: /prometheus/

For details, see the prometheus module documentation.

☸ Dashboard

Get access to the Kubernetes Dashboard.

Web service name: dashboard

👌 Status page

Get information about the overall status of Deckhouse Platform and its components.
Web service name: status

Get detailed SLA statistics for each component and time frame.
Web service name: upmeter

🏭 Going to production

Prepare your cluster to receive traffic.

Use the production readiness checklist to make sure you haven’t forgotten anything.

Deploying your first application

⟳ Setting up a CI/CD system

Create a ServiceAccount to use for deploying to the cluster and grant it all the necessary privileges.

You can use the generated kubeconfig file in Kubernetes with any deployment system.

🔀 Routing traffic

Create a Service and Ingress for your application.

For details, see the ingress-nginx module documentation.

🔍 Monitoring your application

Add prometheus.deckhouse.io/custom-target: "my-app" and prometheus.deckhouse.io/port: "80" annotations to the Service created.

For details, see the monitoring-custom module documentation.

Other features

⚖ Managing nodes

Run the following command to list NodeGroups created in the cluster during the deployment process: d8 k get nodegroups. For details, see the node-manager module documentation.

You only need to make changes to minPerZone and maxPerZone parameters to scale the existing groups. If these two parameters are not equal, Deckhouse will automatically launch an autoscaler.

You need to create a new InstanceClass and a NodeGroup referring to it to create new groups.

Next steps

Detailed information about the system and components is available in the Stronghold documentation.

If you have any questions, contact the Deckhouse online community.