microk8s.enable ingress does not work when context namespace is not default

[asfernandes]

When I set my context namespace to a custom one and use microk8s.enable ingress, the ingress controller objects are created on my namespace.

But when that happens it does not work when I create my ingress. Instead of display 127.0.0.1 in the address field of kubectl get ingress, it shows blank and the address is not accessible.

[balchua]

Oh yes. The service account nginx-ingress-microk8s-serviceaccount in the clusterrolebinding is bound to default namespace. You can try the crb manifest below.

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: nginx-ingress-microk8s
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: nginx-ingress-microk8s-clusterrole
subjects:
- kind: ServiceAccount
  name: nginx-ingress-microk8s-serviceaccount
  namespace: [your custom namespace]

[balchua]

I think fixing the ingress to be in an ingress namespace by default is a better approach. Wdyt?

[asfernandes]

I think microk8s.enable ingress should create the objects in a fixed namespace, not in the one defined in the current context.

[balchua]

@asfernandes yes. I meant the addon should consider using ingress namespace. 😁

[ktsakalozos]

I am +1 to using a fixed namespace for ingress (we could have that configurable with a sane default). Just to confirm we are discussing adding namespaces to the parts of the ingress manifest https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/actions/ingress.yaml, right?

[balchua]

@ktsakalozos yup. That's the one.

[balchua]

We can work on this one after this pr? https://github.com/ubuntu/microk8s/pull/484

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[balchua]

This is fixed now. The ingress is now in ingress namespace.