What is the relationship between Kubernetes containers, Github repositories, and docker registry?

Asked 2 months ago, Updated 2 months ago, 2 views

Thank you for browsing.
I'm a beginner at Kubernetes.

Until now, container technology has been
I have experienced how to publish and operate the service with docker-compose in VPS.


for docker-compose Containers:Github Repository:docker Registry relationship is
n:1:0.
(I didn't use docker registry because docker-compose didn't have any particular reason to make docker registry mandatory)

However, for Kubernetes,
I don't even know the k character of Kubernetes yet, but
Feelings of touch and experience

Containers:Github Repository:docker Registry relationship is
I'm wondering if it's 1:1.
Is this understanding correct?

Other than that, I would appreciate it if you could tell me how it is used in the field!
Currently, I am worried about what kind of project management Kubernetes will do.

docker kubernetes

2022-09-30 11:02

1 Answers

I also use the Docker registry in the Docker/Docker Composer, and I understand that it is at least essential for running container applications in production.

With Compose, this situation can be achieved because it can be built at the time of composition, but I understand that every time I build, the Docker container's portability of "handing moving things over to another environment" is not utilized.

Container: Github Repository: docker registry relationship was n:1:0.

If you're using the Build section in Composer, this may not be wrong, but I don't think the registry is exactly zero (because the base image in the Dockerfile was originally pulled from the registry).

I'm wondering if the relationship between container:Github repository:docker registry is 1:1:1, but is this understanding correct?

The correspondence between the container and the registry that manages the image is n:n, but I don't think that's always the case with the Git repository.

For example, there is an application that is

Front End - [Back End A - Back End B] - [Database A - Database B]

Assume that you are configured with services such as .At this time, DB needs to have both front-end applications and back-end applications, even if it has managed services or MySQL on its own host.

When using containers, it is common for each to act as an independent container, but sometimes it is better to separate repositories for each application if the size is large.

Therefore, I think it is difficult to generalize the relationship between Git's repository and the number of containers.

In addition, Kubernetes has a scaling concept unlike Composer.

In other words, when the backend A is under heavy load, it scales out horizontally according to the conditions.If the number of containers (called Pod in Kubernetes) is increasing due to scale-out, this is not always the same, as this number is not constant.


2022-09-30 11:02

If you have any answers or tips


© 2022 OneMinuteCode. All rights reserved.