“Get https://registry-1.docker.io/v2/”: tls: failed to verify certificate: x509: certificate signed by unknown authority” error in minikube docker
I am using WSL, and there
I am running Kubernetes cluster inside minikube which is running on docker. When I am trying to create a pod, it always shows below error –
Access service on host from pod on minikube
I’m trying to follow this guide: https://minikube.sigs.k8s.io/docs/handbook/host-access/
storage provisioner pod restarts due to Failed to update lock:
storage provision pod restarts when every copy the files from non PV path in the pod to pv path location error in the storage pod
[![enter image description here][1]][1]
How to connect my backend-service using frontend service in minikube
So, the scenario is, I have created two service one is frontend service and another is backend service.
cpu memory error in kubernetes when i try deploy pods
Problem: I cannot start my nginx server cluster, promtail demoset and loki pod to aggregate information.
Kubernetes mounted volume not writable in nested folders
I have created a kubernetes deployment which has a volume mount though a pvc. The volume is properly getting mounted and i am able create files and folders inside the mounted path. but if i try to create a file inside the newly created folder i am getting a permission denied issue. even if i try to modify the permission for the folder, its getting denied.
All the differences between minkube and regular kubernetes
Given a kubernetes release version,
x509: certificate signed by unknown authority Minikube cluster
I deployed a single node minikube cluster with minikube start --vm-driver=none
means running on the bare metal which is a VM. I deploy my own custom scheduler and after running that scheduler I am facing this error