Skip to content

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.

JUMP TO ANOTHER FORUM

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

4 results found

  1. As a developer, I would like to manage my Aiven resources with Crossplane (https://www.crossplane.io/).

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. In order to streamline and automate the deployment of ClickHouse services, it requires the Aiven Operator for Kubernetes to be able to create roles and set them for users

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. As an Aiven admin user who manages resource definitions in Kubernetes using Aiven operator, I want changes further made in Aiven via other APIs to be automatically reconciled, so that desired and actual state remain consistent.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?