Create Kubernetes Manifest

[marshalmiller]

I currently have a Docker Swarm config under production.yml. However, we are running into issues with persistent storage. My experience with Kubernetes is limited, so I would appreciate any help creating the proper config files. I believe this is just a manifest file, but advise if there is more.

[Rajdeep1311]

Sir, I am trying to solve the issue

[Rajdeep1311]

@marshalmiller Hello sir, I am trying to docker-compose up on my local, all the images are pulled except Nginx and gives the following error message " pull access denied for rottingresearch/nginx, repository does not exist or may require 'docker login': denied: requested access to the resource is denied" . I have used docker-login but still the same problem, can you please tell me why so?

[marshalmiller]

Hey @Rajdeep1311! Thank you for taking up this issue. I really appreciate it. The nginx container is a private container only accessible to organizational accounts. This is for security reasons since it exposes some IPs and other things that we don't want public. However, you should not really need it for this. We only use it as an ingress controller, and Kubertenes' version will work much better. So, just delete that image from the yaml file. You can always use the docker-compose.yml file for your basic setup too.

[Rajdeep1311]

Okay sir

[Rajdeep1311]

Sir I have raised a PR, please do check @marshalmiller

[marshalmiller]

@Rajdeep1311. Thank you. Please bear with me because I'm not super familiar with Kubernetes. I think I still need a manifest for the volumes. Perhaps for the ingress as well? I am currently using Portainer to manage the cluster. Documentation. Lastly, is it possible to run both containers in one manifest? The worker doesn't use any ports. It connects directly to the application. Let me know what is and is not possible. Thank you!

[Rajdeep1311]

Can you open my PR? I will see what can I do @marshalmiller

[Rajdeep1311]

Shall I create another PR sir?

[marshalmiller]

@Rajdeep1311 I already merged your PR since no one else is working on those files. Maybe create another one for the edits. If it's not too much trouble. If it's a big deal, I can revert and reopen it.

[Rajdeep1311]

Sir it would be helpful if you reopen sir

[marshalmiller]

@Rajdeep1311 It wouldn't let me revert it, so I created another one; you can use PR #167. #167

[Rajdeep1311]

Sir I changed the PR @marshalmiller

[Rajdeep1311]

Sir please do review my PR @marshalmiller

[marshalmiller]

Hey @Rajdeep1311. I've been reviewing the PR. I didn't want to close it, since last time you wished to reopen it later. The only issue I see so far is that I cannot scale it because the volumes are ReadWriteOnce. Now. That does work. I know need one to write at a time. But the hope was that we could spin up workers to scale with load. Those would need read access to the cache folder. When I changed it to ReadWriteMany, I got a different error about being unable to access the volume because another container was using it. Any suggestions? I'll keep tinkering and see if I can figure it out.

[Rajdeep1311]

I will try to help out sir