Skip to content
← Aiven Ideas

Platform & Experience

Please use this forum to share your ideas on how we can improve in any of these areas.
Join our forum to discuss your ideas with Aiven community or check out our public roadmap.

Platform & Experience

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1 result found

  1. Aiven Operator for Kubernetes to use some other field than metadata.name as the Aiven-side name for the resource

    As an Aiven Operator user
    I would like to specify multiple ServiceUsers, Databases, ConnectionPools same Kubernetes namespace using the same Aiven-name
    So I can for example duplicate a database service but still continue having the same database name and user names for the new service.

    I'd propose to have some under spec that could be used to use as the actual database name or username in place of the metadata.name. Something like Database.spec.databaseName and ServiceUser.spec.userName. Maybe the metadata.name could still be used if the other field is not specified, but specifying it under spec would overwrite what's in metadata. Or…

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Pending Review  ·  0 comments  ·  Aiven Operator for Kubernetes®  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?