Deckhouse Platform in kind
Congratulations, your Deckhouse platform is up and running!
Let’s see what is available in the monitoring module.
-
Grafana is available at grafana-127-0-0-1.nip.io.
Access to Grafana is restricted via the basic authentication mechanism (additional authentication options are provided in the user-auth module:
- Login —
admin
; - Password — generated automatically. It can be found in the
deckhouse
ConfigMap in the configuration section of theprometheus
module. Use the following command to get it:kubectl -n d8-system get cm deckhouse -o jsonpath="{.data.prometheus}" | grep password
Sample output:
$ kubectl -n d8-system get cm deckhouse -o jsonpath="{.data.prometheus}" | grep password password: UJvSB4UYTa3fnDOco6LF
Explore Grafana dashboards bundled with Deckhouse.
- Login —
-
Prometheus is available at grafana-127-0-0-1.nip.io/prometheus/.
Deckhouse, deployed in the kind cluster, is suitable for getting acquainted with other features that might need for production environments. Read further about such Deckhouse features.
Essentials
Dashboard
Enable the dashboard module and get access to the Kubernetes Dashboard at: dashboard-127-0-0-1.nip.io.
You need to enable the user-authz module for Dashboard to work.
Status page
Enable the upmeter module and get information about the overall status of Deckhouse and its components at status-127-0-0-1.nip.io.
At the upmeter-127-0-0-1.nip.io page you can get detailed SLA statistics for each component and time frame.
Deploying your first application
Deckhouse makes it easier to set up CI/CD system access to a cluster to deploy your application and allows your application to be monitored by custom metrics.
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.
External authentication
Deckhouse supports various external authentication mechanisms.
Configuring DexProvider
You have to configure a
DexProvider
object to enable, e.g., GitHub-based authentication. After creating the DexProvider
object, all access attempts to Deckhouse components such as Grafana, Dashboard, etc.,
will be authenticated using GitHub.
External authentication for any Ingress
You have to create a DexAuthenticator object to enable external authentication for any Ingress resource.
External authentication for the Kubernetes API
Configure
publishAPI
, download kubectl
and create a kubeconfig
file for external access to the API using the web interface available at kubeconfig.example.com
.
What’s next?
Detailed information about the system and the Deckhouse Platform components is available in the documentation.
Please, reach us via our online community if you have any questions.