You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently services are exposed either via ClusterIP or LoadBalancer.
For security reasons we usually use NodePort and only expose it to VPC via firewall rules.
In our use case we use ExternalDNS operator to keep nodes IP up to date.
That way our other k8s clusters and/or resources can connect to the DB without using Public IP.
It would be awesome if we could enable node port via UI as well.
The only way to make it work right now is to patch k8s resources once they are created.
The text was updated successfully, but these errors were encountered:
Currently services are exposed either via ClusterIP or LoadBalancer.
For security reasons we usually use NodePort and only expose it to VPC via firewall rules.
In our use case we use ExternalDNS operator to keep nodes IP up to date.
That way our other k8s clusters and/or resources can connect to the DB without using Public IP.
It would be awesome if we could enable node port via UI as well.
The only way to make it work right now is to patch k8s resources once they are created.
The text was updated successfully, but these errors were encountered: