apiserver | Prototype NII Data- API '' Service

If your image has a latest tag, the Pod's ImagePullPolicy will be automatically set to Always. Each time the pod is created, Kubernetes tries to pull the newest image.

Try not tagging the image as latest or manually setting the Pod's ImagePullPolicy to Never. If you're using static manifest to create a Pod, the setting will be like the following:

This seems to be a bug introduced with 1.25.0 version of minikube: https://github.com/kubernetes/minikube/issues/13503 . A PR to revert the changes introducing the bug is already open: https://github.com/kubernetes/minikube/pull/13506

The fix is scheduled for minikube v1.26.

This sounds very similar to what I encountered when we had a misbehaving webhook.

If you have a massive number of jobs all showing as active, but no pods appearing, or pods taking a long time to appear, then that's a sign of an admission webhook interfering with the pod creation. If it's a cronjob affected, you will get a "snowball" effect:

Writeup: https://blenderfox.com/2020/08/07/the-snowball-effect-in-kubernetes/

Kubernetes Issue: https://github.com/kubernetes/kubernetes/issues/93783

As for fixing your issue, you need to find out what is interfering with the creation (in our case, we had an up9 webhook misbehaving. Disabling that allowed the creation of the pods)

based on the iconic Failed to create SSL Connection output in the logs, I assume that you have run into the dreaded The demo certificates included in the Hono chart have expired problem.

The Cloud2Edge package chart is being updated currently (https://github.com/eclipse/packages/pull/337) with the most recent version of the Ditto and Hono charts (which includes fresh certificates that are valid for two more years to come). As soon as that PR is merged and the Eclipse Packages chart repository has been rebuilt, you should be able to do a helm repo update and then (hopefully) succesfully install the c2e package.

The solution for the issue is to regenerate the kubeconfig file for the admin:

I was able to find the solution to my problem, although, I'm not really sure what was the main issue, it seems that it was related to old configurations in the .minikube folder in the users' home directory.

To fix it, first I had to enabled Kubernetes in docker desktop, and then I had to stop and delete minikube cluster, and finally delete the directory. Then running the command again was successful.

To fix:

What you have defined is only control the service account. Here's a tested spec; create a yaml file with:

Even in an empty cluster with just one master node, there are at least 5 components that reach out to the API server on a regular basis:

• kubelet for the master node
• Controller manager
• Scheduler
• CoreDNS
• Kube proxy

This is because API Server acts as the only entry point for all components in Kubernetes to know what the cluster state should be and take action if needed.

If you are interested in the details, you could enable audit logs in the API server and get a very verbose file with all the requests being made. How to do so is not the goal of this answer, but you can start from the apiserver documentation.

Turned out there were several issues:

• I was using Ubuntu Buster which is deprecated.
• My client/server Kubernetes versions were +/-0.3 out of sync
• I was following outdated instructions

I reinstalled the whole cluster following Kubernetes official guide and, with a few snags along the way, it works!