2 results found
-
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…
3 votes -
Aiven Operator needs to support Aiven for Valkey
As a platform developer
I want to create new Aiven for Valkey services using the aiven-operator
so that I can migrate my applications away from Aiven for Caching (Redis) before Redis EOL.1 vote
- Don't see your idea?