Some ingress controllers run outside of the cluster (AWS ALB) and require that the service be exposed via NodePort. Today Acorn only supports Cluster IP and LoadBalancer types.
One possible solution could be defining a top level acorn.io/ingress-class resource type that specifies k8s ingress class and service types that should be created to interact with it. The default should be clusterIP, and optionally allow nodeport.
If an acorn.io ingress class isn't defined we should fall back to the current behavior.
Some ingress controllers run outside of the cluster (AWS ALB) and require that the service be exposed via NodePort. Today Acorn only supports Cluster IP and LoadBalancer types.
One possible solution could be defining a top level
acorn.io/ingress-class
resource type that specifies k8s ingress class and service types that should be created to interact with it. The default should be clusterIP, and optionally allow nodeport.If an acorn.io ingress class isn't defined we should fall back to the current behavior.