Can I connect to my cluster nodes with SSH?
To provide consistency and predictability of service for Civo managed Kubernetes, SSH connections to the cluster nodes are not supported. While there are documented ways for you to execute into nodes given the credentials you already have, any changes you make this way risk breaking your cluster or preventing access to it, and are not supported. If you want to fully customize your cluster, you can create one using our infrastructure-as-a-service instances as nodes.
Another reason there is no SSH access is that we want to keep our options open about moving the architecture of the managed Kubernetes service to a virtualised platform such as
k3v or similar in the future, and thus want to make sure users will experience a consistent service.
Why can't I see my cluster nodes on the instances page?
Related to the question above, because the nodes themselves are not accessible via SSH or managed outside the cluster, they will not appear as separate instances. If you need to restart a particular node, you can click on the "recycle" button on the cluster interface page.
Can I start a cluster without any pre-installed applications?
Civo Kubernetes runs the K3s distribution of Kubernetes. By default, K3s starts with
Traefik as an Ingress Controller on all new clusters. This is to allow connections to your cluster without extra configuration on your part. You can prevent Traefik from being installed when you start a cluster by deselecting it in the web UI (under 'Architecture') or by adding
--remove-applications=Traefik to your Civo CLI cluster creation command.
Remember that starting up a cluster with no Ingress Controller means you will manually have to configure one to allow access to applications.
Do all nodes on Kubernetes clusters have public IP addresses?
Your cluster has one public IP address. It receives traffic to your cluster, and routes it to your worker nodes in the form of a load balancer. This is part of the control plane functionality managed by Civo.
Can I change the underlying operating system running Kubernetes?
We aim for the underlying operating system to be as lightweight as possible to allow for maximum resources to be allocated to Kubernetes and your applications. To this end, we may change the underlying OS, but as this is a managed service this will be the same for all users.
Can I pool different-sized nodes into the same cluster?
You can create node pools of different nodes. This means that you can have nodes of different sizes (e.g. 2x medium, 2x large) in the same cluster, and they get labelled for your convenience. On your cluster, you will see node pools illustrated like this:
Can I remove an installed marketplace application?
At the moment, the only way to remove a marketplace application is to remove it by running
kubectl delete -f on the resource and manifest files. Please note that while the marketplace application will get removed from your cluster, this will not be reflected on the web UI for the moment.
We are working on a new version of the Application Marketplace which would allow for installation and uninstallation at will.
Why does a Civo Kubernetes cluster come with an ingress controller bundled in?
The lightweight Kubernetes distribution we use, K3s, bundles a few components into a cluster. This is to allow developers and users the quickest way to get up and running. K3s is an opinionated but flexible distribution of Kubernetes. If you are curious about the differences between K3s and K8s,
our CTO Andy wrote a great post about precisely this topic, and why we decided to go with Rancher's k3s as the Kubernetes distribution of choice.
k3s is fully compatible with upstream Kubernetes (K8S).