Deckhouse Kubernetes Platform on OpenStack
Congratulations, your Deckhouse Kubernetes Platform is up and running!
Now that you have installed and properly configured Deckhouse, let’s look at what you can do with it.
By default, the Dex is used for accessing all the components.
Here are credentials generated in the previous steps:
- Username —
- Password —
<GENERATED_PASSWORD>(you can also find it in the
UserCustomResource in the
Use them to access the web interface of the Deckhouse components.
The documentation for the installed in your cluster version of Deckhouse.
Web service name: documentation
Explore Grafana dashboards bundled with Deckhouse.
Web service name: grafana
To access Prometheus: /prometheus/Learn more about the
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
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
Ingress for your application.
Learn more about the capabilities of the
🔍 Monitoring your application
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.
⚖ Managing nodes
Run the following command to list nodegroups created in the cluster during the deployment process:
kubectl get nodegroups. For more information, see the node-manager’s documentation.
You only need to make changes to
maxPerZone parameters to scale the existing groups. If these two parameters are not equal, Deckhouse will automatically launch an autoscaler.
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.