Deckhouse Platform in a private environment
Congratulations, your Deckhouse 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 —
Use them to access the web interface of the Deckhouse components.
Up-to-date Deckhouse documentation in your cluster
The in-cluster documentation for a specific version of Deckhouse used in your cluster is available at deckhouse.example.com.
The Kubernetes Dashboard is available at: dashboard.example.com
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.
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.
Deckhouse supports various external authentication mechanisms.
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
publishAPI, download kubectl
and create a
kubeconfig file for external access to the API using the web interface available at
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.