Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for privatelink urls? #751

Open
christoffer-eide opened this issue Jun 12, 2024 · 0 comments
Open

Support for privatelink urls? #751

christoffer-eide opened this issue Jun 12, 2024 · 0 comments
Labels
customer request Reported by a customer, but opened by Aiven staff

Comments

@christoffer-eide
Copy link
Contributor

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
@byashimov byashimov added the customer request Reported by a customer, but opened by Aiven staff label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer request Reported by a customer, but opened by Aiven staff
Projects
None yet
Development

No branches or pull requests

2 participants