Deckhouse Kubernetes Platform in existing cluster

1
Selecting infrastructure
2
Installation information
3
Installation
4
Finishing installation
5
What can I do next?

Everything is installed, configured, and working!

Now that you have installed and properly configured Deckhouse Kubernetes Platform, let’s look at what you can do with it.

For access to the in-cluster documentation the deckhouse domain is reserved in accordance with the DNS names template. E.g., for the DNS names template %s.1.2.3.4.sslip.io, the documentation web interface will be available at https://deckhouse.1.2.3.4.sslip.io.

Access to the documentation is restricted via the authentication mechanism (additional authentication options are provided in the user-auth module):

  • Login — admin

  • Password was generated automatically. You can find it out by running the command:

    • For Deckhouse 1.46 or newer:

      kubectl -n d8-system exec svc/deckhouse-leader -c deckhouse -- sh -c "deckhouse-controller module values documentation -o json | jq -r '.internal.auth.password'"

    • For Deckhouse 1.45 or older:

      kubectl -n d8-system exec svc/deckhouse-leader -c deckhouse -- sh -c "deckhouse-controller module values deckhouse-web -o json | jq -r '.deckhouseWeb.internal.auth.password'"

Sample output...

$ kubectl -n d8-system exec svc/deckhouse-leader -c deckhouse -- sh -c "deckhouse-controller module values documentation -o json | jq -r '.internal.auth.password'" 
3aE7nY1VlfiYCH4GFIqA

Essentials

📊 Monitoring

Explore Grafana dashboards bundled with Deckhouse.

Web service name: grafana

To access Prometheus: /prometheus/

Learn more about the monitoring module.

☸ Dashboard

Get access to the Kubernetes Dashboard.

Web service name: dashboard

👌 Status page

Get information about the overall status of Deckhouse 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 our 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.

Learn more about the capabilities of the ingress-nginx module.

🔍 Monitoring your application

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

For more information, see the monitoring-custom module’s documentation.

What’s next?

Detailed information about the system and the Deckhouse Kubernetes Platform components is available in the documentation.

Please, reach us via our online community if you have any questions.

Go back