This is generic docker debugging help. I've installed minikube, but haven't ran into this particular inconvenience.
When it says "consider investigating Docker's performance/health" it probably means to check the docker logs
docker ps --all
should give you a list of images, if this is your only docker project, then it oughta be easier to find. The ...
There are multiple ways to expose Dashboard through traefik.
Traefik terminates HTTPS from client and as client opens new HTTPS request to Dashboard.
+-------------+ HTTPS +-------------+ HTTPS +-------------+
| Client -----(session 1)----- Traefik ------(session 2)---- Dashboard |
The most stable way to assure you're deploying a consistent image is to use the digest instead of tags. The digest is like the git sha of a container image. This assures that if someone uploads a new image and tags it with an existing version tag, either accidentally or maliciously, you will continue to pull the known good image. The drawback is digests are ...
First a couple key points:
Tags are mutable in most registries, so v1 today may be different from v1 a month ago. However clients do need to pull this tag again to see the updates.
Multiple tags may point to the same image. So stable and v1 could point to the same image.
Pointing to a digest ensures the image is immutable, however you will not receive ...
The error you are getting is from your Kubernetes cluster being unable to pull container image from GitLab.
Providing a temporary credential to pull the containers as deploy time is not a great solution. For example, say your Kubernetes cluster needs to scale up by adding another node, the node will come up and try and pull the container, but the secret will ...
I would say the reason you are wanting to develop against Kubernetes locally is to see how the application works with within the pod, and how it interacts with other dependencies inside the Kubernetes instance.
In this case you want to go for speed of getting the code into the container. Here you want something like Tilt Live Update which will run your build ...
What does 'kubectl top node' return for your node usage?
Kubernetes is pretty low overhead and can certainly handle more than 15req/s. Does your application rely on a database? If so, where is that database living? Is that single node also running any other pods?
As others noted, an APM would be a helpful tool to diagnose unexpected performance issues.
It's really up to your personal preference, but for minikube you can certainly follow the same standards that you would for production.
If your production environment will use some sort of volume mount for your application code, then follow that same workflow for local dev and just have a pod running that mounts to your local code.
If your production ...
If you could let us know what helm chart you have used to install prom-operator, that might help refine the answer.
But in case of kube-prometheus-stack, in the values.yaml of the , use the additionalScrapeConfigs section to describe jobs that are external to k8s system and re-deploy.
Or use serviceMonitors as described in this article