Support for privatelink urls?

[christoffer-eide]

We have enabled AWS private link for some of our kafka and postgres services. In the aiven console, we can view both the "dynamic" (regular) urls, and the private link urls.

When we create a ServiceUser, the generated secret contains only the dynamic/regular urls:

apiVersion: v1
kind: Secret
data:
  HOST: <pg-service-name>-<aiven-project>.aivencloud.com
  PORT: 26586

This makes it cumbersome for our dev teams to use the operator, as they need to use USENAME, PASSWORD and CA_CERT from the generated secret and configure the HOST elsewhere.

Would it be possible to get the operator to use the privatelink urls (if available) in the genererated secret?

apiVersion: aiven.io/v1alpha1
kind: ServiceUser
spec:
  connInfoSecretTarget:
    name: generated-secret-name
    usePrivateLinkIfAvailable: true

[mikkoc]

this would be nice to have 👍

[msidd]

+1 This would significantly streamline the workflow for our development team