Is your feature request related to a problem? Please describe.
When working in self-hosted environment, we route all traffic through ingress controller. The nodes are unaccessible on NodePort nor LoadBalancer provisioner is available. Setting service type to ClusterIP makes the destination point to internal cluster IP.
Describe the solution you'd like
Allow for configuring custom destination address, eg. infrahq.cluster.domain:443.
Describe alternatives you've considered
Installing LoadBalancer provisioner, exposing NodePort
Environment Details
$ infra version
Client: 0.21.0
$ kubectl version
Client Version: v1.28.2
Server Version: v1.28.0
Self-hosted cluster
Additional context
Probably already possible via endpointAdds (https://github.com/infrahq/infra/blob/main/dev/connector.yaml#L12C1-L12C1) just not exposed in values.yaml
Is your feature request related to a problem? Please describe.
When working in self-hosted environment, we route all traffic through ingress controller. The nodes are unaccessible on NodePort nor LoadBalancer provisioner is available. Setting service type to
ClusterIPmakes the destination point to internal cluster IP.Describe the solution you'd like
Allow for configuring custom destination address, eg.
infrahq.cluster.domain:443.Describe alternatives you've considered
Installing LoadBalancer provisioner, exposing NodePort
Environment Details
Self-hosted cluster
Additional context
Probably already possible via
endpointAdds(https://github.com/infrahq/infra/blob/main/dev/connector.yaml#L12C1-L12C1) just not exposed in values.yaml