microk8s | MicroK8s is a small , fast , single-package Kubernetes

I have transferred my microk8s setup to a new server and found that the once-working ingress setup my trial setup stopped working.

I am running this minimal whoami-app:

Here is the issue: We have several microk8s cluster running on different networks; yet each have access to our storage network where our NAS are.

within Kubernetes, we create disks with an nfs-provisionner (nfs-externalsubdir). Some disks were created with the IP of the NAS server specified. Once we had to change the IP, we discovered that the disk was bound to the IP, and changing the IP meant creating a new storage resource within.

To avoid this, we would like to be able to set a DNS record on the Kubernetes cluster level so we could create storage resources with the nfs provisionner based on a name an not an IP, and we could alter the DNS record when needed (when we upgrade or migrate our external NAS appliances, for instance) for instance, I'd like to tell every microk8s environnements that:

192.168.1.4 my-nas.mydomain.local

... like I would within the /etc/hosts file.

Is there a proper way to achieve this? I tried to follow the advices on this link: Is there a way to add arbitrary records to kube-dns? (the answer upvoted 15 time, the cluster-wise section), restarted a deployment, but it didn't work

I cannot use the hostAliases feature since it isn't provided on every chart we are using, that's why I'm looking for a more global solution.

Best Regards,

Usually i am able to find most things by searching on the web - however in this case, the instructions on the web talk about - probably very basic stuff that i don't get yet.

What i am trying to achieve: i am trying to install argocd, using microk8s and nginx-ingress. Right now i am stuck at enabling the SSL passthrough for argocd. Currently i configured an ingress-controller according to the instructions of the argocd-documentation and the ingress-controller runs without errors.

My guess is that as it's mentioned everywhere that i have to start the ingress controller with the "--enable-ssl-passthrough"-flag.

https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#ssl-passthrough "SSL Passthrough is disabled by default and requires starting the controller with the --enable-ssl-passthrough flag."

Now my problem: How do i do that? - for me, the ingress controller is "just always running". I can delete and recreate the controller with the kubectl-command "create -f ingress.yaml" - which creates an ingress within the argocd-namespace.

i kind of lack the basics of kubernetes and don't get how i could stop and restart the ingress-controller with flags (perhaps i mistake what the "ingress controller" is too). Does anyone have an idea how i could achieve that?

I am running microk8s v1.23.1 on Ubuntu 18.04.3 LTS

I am running into a very strange issue, I cannot set single quotes that are required by Content-Security-Policy. I assume I was running an older version of ingress which only got updated after I disabled and re-enabled it (microk8s).

I'm trying to deploy an elixir (phoenix) application in a microk8s cluster namespace with TLS using let's encrypt. The cluster is hosted on an AWS EC2 instance.

• The ingress is created in the namespace
• ingress routes to the correct domain
• the application is working and displayed on the given domain

The TLS secret is not being created in the namespace and a 'default' one is created

The secrets after deploying both phoenix app and httpbin app:

When i do this command kubectl get pods --all-namespaces I get this Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.

All of my pods are running and ready 1/1, but when I use this microk8s kubectl get service -n kube-system I get

I would like to deploy an ngingx-ingress controller on my self-hosted Kubernetes (microk8s) that is configurable to listen on one or more interfaces (external IPs).

Not even sure if that is easily possible and I should just switch to an external solution, such as HAProxy or an nginx.

Required behavior:

I have a Docker container with MariaDB running in Microk8s (running on a single Unix machine).

I have a Docker Swarm running a container with our custom code (.net core 3.1 on Linux) in with no issue. I have just setup a test 4 node Kubernetes cluster using Microk8s. When I load the image to Kubernetes, it appears to go through fine but the container starts and then stops immediately with error "Back-off restarting failed container". Looking at the error from the pod, I get "It was not possible to find any installed .NET Core SDKs. Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from: https://aka.ms/dotnet-download".

The image is the same image running in the Swarm. My searches have led me to ENTRYPOINT potentially being the issue from the build dockerfile but I haven't had any luck with with changes to this. I have put my dockerfile below in case it is relevant to this problem.