kubernetes

Your repository is private and requires login to pull image.

You need to create a registry credentials secret for kubernetes, as it do not uses docker credentials.

See https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

1. Create a secret named regcred:

Based on the storage class spec, I think the problem is the volumeBindingMode being set as WaitForFirstConsumer which means the PV will remain unbound until there is a Pod to consume it.

You can change it Immediate to allow the PV to be bound immediately without requiring to create a Pod.

You can read about the different volume binding modes in detail in the docs.

Kubernetes is a container orchestrator that may use Docker as its container runtime. So, they are quite different things—essentially, different levels of abstraction.

You could theoretically run an application at both of these abstraction levels. Here's a comparison:

Docker

You can run an application as a Docker container on any machine that has Docker installed (i.e. any OS or cloud provider instance that supports Docker). However, you would need to implement any operations-related features that are relevant for production, such as health checks, replication, load balancing, etc. yourself.

Kubernetes

Running an application on Kubernetes requires a Kubernetes cluster. You can run a Kubernetes cluster either on-premises, in the cloud, or use a managed Kubernetes service (such as Amazon EKS, Google GKE, or Azure AKS). The big advantage of Kubernetes is that it provides all the production-relevant features mentioned above (health checks, replication, load balancing, etc.) as part of the platform. So, you don't need to implement them yourself but just use the primitives that Kubernetes provides to you.

Regarding your two requirements, Kubernetes provides both of them, while using Docker alone does not provide easy production-readiness (requirement 2). So, if you're opting for production stability, setting up a Kubernetes cluster is certainly worth the effort.

You need to create the StorageClass object -

Routing within the app should be handled by the app. So, there should be no need to define dynamic paths. Try this.

Short answer: No
But it's complicated.

nginx image you mentioned is one of the most popular images (5th on the Docker Hub, by the time of this writing), is relatively small (133MB), and is easy to remember. That's why it is widely used as an example in many tutorials.

Isn't ingress-nginx capable to do all work as nginx image?

To some extent.
Pod and Ingress are different Kubernetes resources, and they act differently. nginx image is usually deployed as a container inside a pod.

In case of nginx ingress controller, similiar image is used for both Pod and Ingress (mentioned below).

Whenever you deploy (for example) a rewrite rule in ingress controller

It turned out that my local docker registry wasn't visible from kubernetes. kubectl get events shows InternalError "Unable to fetch image ... "

If you want to use kubernetes inside a docker container my suggestion is to use k3d .

k3d is a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker.k3d makes it very easy to create single- and multi-node k3s clusters in docker, e.g. for local development on Kubernetes.

You can Download , install and use it directly with Docker. For more information you can follow the official documentation from https://k3d.io/ .

To get the list of pods you dont' need to create a k8s cluster inside a docker container . what you need is a config file for any k8s cluster . ├── Dockerfile ├-- config └── main.py 0 directories, 3 files

after that :

I think that the answer is to use external-dns.

ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way.