Deckhouse Kubernetes Platform on Zvirt
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 —
admin@deckhouse.io
- Password —
<GENERATED_PASSWORD>
(you can also find it in theUser
CustomResource in theresource.yml
file)
Use them to access the web interface of the Deckhouse components.
Essentials
📚 Documentation
The documentation for the installed in your cluster version of Deckhouse.
Web service name: documentation
📊 Monitoring
Explore Grafana dashboards bundled with Deckhouse.
Web service name: grafana
To access Prometheus: /prometheus/
Learn more about themonitoring
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
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.
Other features
⚖ 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 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.
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.