When attaching a cluster, Kommander federates certain platform services on the newly attached cluster. Operators can use the Kommander UI to customize which platform services to deploy to the attached clusters in a given workspace.
On attachment, three factors impact successfully deploying a platform service on the attached cluster:
- Is the attached cluster a Konvoy cluster or not? For example, a cluster deployed using AWS EKS.
- Is the platform service enabled in the Workspace Platform Services settings?
- Does the platform service support the version of Kubernetes running on the cluster?
The following tables describe the list of platform services that are federated on attachment, along with the versions of Kubernetes that they support. If the cluster is running a version of Kubernetes that is not in the supported list, the platform service is not federated to that cluster. If the platform service description indicates
only federated on non-Konvoy clusters, the platform service is not installed into Konvoy clusters, since it is by default installed with Konvoy using Kubernetes Base Addons.
Currently, the monitoring stack is federated by default and the logging stack is not.
Review the workspace platform service resource requirements to ensure the attached clusters have sufficient resources.
Customize a workspace’s platform services
If you can edit a workspace, you can customize the platform services federated to a workspace’s clusters using the Kommander UI. Access the settings page by going to the specific workspace’s Dashboard page, selecting the Actions drop-down button on the top right of the Dashboard, and selecting Edit Workspace Platform Services.
This takes you to the settings page which provides lists of platform services that you can enable or disable along with descriptions of the services.
Platform services support a specific set of Kubernetes versions running on the attached cluster. See the column
Kubernetes Versions Supported in the below chart for supported Kubernetes versions per platform service. Platform services will not be deployed to clusters running Kubernetes versions outside of those listed.
If desired, the Kubeaddons Controller can also be disabled, though it is highly discouraged. All platform services require the controller in order to be installed properly. You can find the setting to turn the controller off at the bottom of the page underneath the
Foundational Components header. Disabling the controller will automatically disable all platform services.
Workspace platform services
|Name||Federated by default||Supported Kubernetes Versions||Only federated on non-Konvoy clusters|
|cert-manager||True||1.16 - 1.20||True|
|elasticsearch||False||1.16 - 1.20||True|
|elasticsearch-curator||False||1.16 - 1.20||True|
|elasticsearchexporter||False||1.16 - 1.20||True|
|fluentbit||False||1.16 - 1.20||True|
|kibana||False||1.16 - 1.20||True|
|kube-oidc-proxy-kommander||True||1.16 - 1.20||False|
|kubecost||True||1.16 - 1.20||False|
|prometheus||True||1.16 - 1.20||True|
|prometheusadapter||True||1.16 - 1.20||True|
|reloader||True||1.16 - 1.20||True|
|traefik||True||1.16 - 1.20||True|
|traefik-forward-auth||True||1.16 - 1.20||False|