NodePort Service Type for K8S Charm?

Playing around with different ingress controllers trying to find the best fit for a way into some services I’ve deployed on my k8s at the datacenter. I’m wondering if it possible to set NodePort as the service type for a k8s charm?

It’s not currently supported in charm metadata but you can use

--config kubernetes-service-type=NodePort

when deploying.

Charm metadata only currently supports “cluster”, “external”, “loadbalancer”.

1 Like