E2E Kubernetes is managed Kubernetes in MyAccount. You choose a Kubernetes version, a master node, and one or more worker node pools, and E2E builds the cluster on E2E nodes in your VPC, in Delhi or Chennai. The master node runs the Kubernetes control plane. Your applications run on the worker nodes, which are grouped into pools: each pool has its own plan and its own way of scaling. You work with the cluster through kubectl, using the kubeconfig file you download from the cluster’s page in MyAccount.
What you can do
Section titled “What you can do”- Create a cluster with a Kubernetes version, pools, a VPC, and a security group.
- Connect to a cluster with kubectl, and open the Kubernetes Dashboard with the cluster’s token.
- Manage node pools: add, resize, and delete pools, act on worker nodes, and set labels and taints.
- Configure autoscaling for a node pool on CPU, on a metric you send, or on a schedule.
- Expose a service with a load balancer, using public service IPs or private LB IPs from the cluster’s LB IP Pool.
- Use persistent volumes, storage that is kept when pods restart, in Delhi.
- Manage a cluster’s security groups, which control traffic to the master and every worker node.
- Renew the cluster certificate that kubectl connects with.
- Upgrade the master plan to give the master node more vCPU and RAM.
- Install marketplace apps on a cluster: a monitoring stack, cert-manager, or the NGINX Ingress Controller.
- Back up a cluster with Velero to an E2E Object Storage bucket, and restore it.
- Monitor a cluster with graphs, alerts, and the activity timeline.
- Use committed billing for a cluster on the master node and on static pools.
- Delete a cluster when you have finished with it.
Where to start
Section titled “Where to start”Get started with Kubernetes. If something goes wrong, see Troubleshooting Kubernetes; for short answers, see Kubernetes FAQ, which also explains how a cluster is billed.