hostpath-provisioner | Dynamic Provisioning of Kubernetes HostPath Volumes

The local mount you created mounts the specified directory into minikube, but not from the guest to the host as you would like it to.

Depending on your host machine's OS you will have to set up proper file sharing using either host folder sharing or a network based file system.

With a bit of work, one could set up Syncthing between the host and the guest VM for persistent file synchronization.

Grab the latest release of Syncthing for your operating system & unpack it (if you use Debian/Ubuntu you may want to use the Debian repository)

At this point Syncthing will also have set up a folder called Default Folder for you, in a directory called Sync in your home directory (%USERPROFILE% on Windows). You can use this as a starting point, then remove it or add more folders later.

The admin GUI starts automatically and remains available on http://localhost:8384/. Cookies are essential to the correct functioning of the GUI; please ensure your browser accepts them.

On the left is the list of “folders”, or directories to synchronize. You can see the Default Folder was created for you, and it’s currently marked “Unshared” since it’s not yet shared with any other device. On the right is the list of devices. Currently there is only one device: the computer you are running this on.

For Syncthing to be able to synchronize files with another device, it must be told about that device. This is accomplished by exchanging “device IDs”. A device ID is a unique, cryptographically-secure identifier that is generated as part of the key generation the first time you start Syncthing. It is printed in a log, and you can see it in the web GUI by selecting “Actions” (top right) and “Show ID”.

Two devices will only connect and talk to each other if they are both configured with each other’s device ID. Since the configuration must be mutual for a connection to happen, device IDs don’t need to be kept secret. They are essentially part of the public key.

To get your two devices to talk to each other click “Add Remote Device” at the bottom right on both devices, and enter the device ID of the other side. You should also select the folder(s) that you want to share. The device name is optional and purely cosmetic. You can change it later if desired. Once you click “Save” the new device will appear on the right side of the GUI (although disconnected) and then connect to the new device after a minute or so. Remember to repeat this step for the other device.

At this point the two devices share an empty directory. Adding files to the shared directory on either device will synchronize those files to the other side.

What is Syncthing: https://syncthing.net/

Installation Guide: https://docs.syncthing.net/intro/getting-started.html

Lates Release of syncthing: https://github.com/syncthing/syncthing/releases/tag/v1.18.5

Debian Repo: https://apt.syncthing.net/

The logs you provided show that you have an incorrectly set parameter wiredTigerCacheSizeGB. In your case it is 0.1, and according to the message

I found the problem. Since the "host-provisioner" takes care of creating PV we should not pass the volumeName in our PVC yaml file. When I removed that field the provisioner could make a PV and bound my PVC to it and now my pod has started.

Now my PVC is:

TL;DR

There are some ways to fix your Ingress so that it would get the IP address.

You can either:

• Delete the kubernetes.io/ingress.class: nginx and add ingressClassName: public under spec section.
• Use the newer example (apiVersion) from official documentation that by default will have assigned an IngressClass:
  • Kubernetes.io: Docs: Concepts: Services networking: Ingress

Example of Ingress resource that will fix your issue:

In microK8s you should be using http://127.0.0.1/microbot to access a pod via ingress from outside the cluster i.e a browser. This is giving you 502 error in nginx ingress controller log. Few things to check

1. Check the service has got Endpoints reflecting correct POD IP using kubectl describe svc microbot -n development

2. Check if container inside pod is listening on port 8080. Maybe it's 80 or something else.

3. The application running as a container in the pod need to listen on 0.0.0.0 instead of 127.0.0.1