Enable custom service annotations for EKS WgGatewayServerTemplate #3273

Is there an existing issue for this?

• I have searched the existing issues

Version

v1.1.2

What happened?

The current helm chart hardcodes these annotations in the WgGatewayServerTemplate when it determines the release is for an AWS/EKS cluster.

For EKS clusters with custom network architectures, it's possible that these annotations are not desired nor supported.

Most notably, I'd want to have control over whether the NLB is provisioned internet-facing or internal, but this is currently forcing us to set it to internet-facing.

I think we should have the ability to either override those annotations (not just append to them like so).

Relevant log output

How can we reproduce the issue?

Define an overriding helm values.yaml like so:

authentication:
  awsConfig:
    useExistingSecret: true
    accessKeyId:
      secretKeyRef:
        name: "liqo-eks-auth"
        key: "access-key-id"
    secretAccessKey:
      secretKeyRef:
        name: "liqo-eks-auth"
        key: "secret-access-key"

Run helm template --release-name liqo/liqo -f helm/values.yaml -n liqo > generated.yaml and see the outputted WgGatewayServerTemplate manifest.

Provider or distribution

EKS

CNI version

No response

Kernel Version

No response

Kubernetes Version

v1.33.8

Code of Conduct

• I agree to follow this project's Code of Conduct