You want to use Google’s Autopilot for your gitlab runners, but your job/builds fail because of low resources (ie ephemeral storage).
You can use a limit range to increase the limits for ephemeral storage or/and memory that will make Google’s autopilot to use them and scale them appropriately.
Create a limit range file like:
And then apply it to your cluster
kubectl -n namespace apply -f limit_range.yaml
You are trying to set up kubernetes on your local machine but trying to use initialize it with kubeadmin init, returns the following error:
[init] Using Kubernetes version: v1.18.3
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR Swap]: running with swap on is not supported. Please disable swap
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
Switch the swap to off (Ubuntu command below) and try again.
You would like to follow the example for working with skaffold by using the skaffold dev command but you are getting the following error:
kosmas:getting-started (master)$ skaffold dev
WARN Your Skaffold version might be too old. Download the latest version (1.0.1) at https://storage.googleapis.com/skaffold/releases/latest/skaffold-linux-amd64
Download the latest release from here https://github.com/GoogleContainerTools/skaffold/releases and follow the instructions for installing it in your system (ie linux):
curl -Lo skaffold https://storage.googleapis.com/skaffold/releases/v1.0.1/skaffold-linux-amd64 && chmod +x skaffold && sudo mv skaffold /usr/local/bin
You get the following error when trying to start minikube:
Error setting up kubeconfig: writing kubeconfig: Error writing file : open : no such file or directory
Unset the KUBECONFIG variable like:
You want to use the kubectl to get your cluster information but you are getting the following error message
$ kubectl cluster-info
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
The connection to the server localhost:8080 was refused - did you specify the right host or port?
That could happen if you have already setup kubectl before or have used a different environment.
So you will need to first unset the environment variable KUBECONFIG with:
$ unset KUBECONFIG
and then use the gcloud client to set your environment again:
$ gcloud container clusters get-credentials your_cluster_name --zone europe-west2-a --project your_project_name
So after this you should be able to use kubectl to get the cluster information
kubeconfig entry generated for your_cluster_name.
$ kubectl cluster-info
Kubernetes master is running at https://xxx.xxx.xxx.xxx
GLBCDefaultBackend is running at https://xxx.xxx.xxx.xxx/api/v1/namespaces/kube-system/services/default-http-backend:http/proxy
Heapster is running at https://xxx.xxx.xxx.xxx/api/v1/namespaces/kube-system/services/heapster/proxy
KubeDNS is running at https://xxx.xxx.xxx.xxx/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://xxx.xxx.xxx.xxx/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy