aws-controllers-k8s
ACK for RDS to support `RestoreDBClusterToPointInTime`
Is your feature request related to a problem? I would like to be able to create DBCluster's from a latest restorable time based on an existing DBCluster.
I'd like to be able to combine the ACK for RDS controller with something like the ArgoCD ApplicationSet controller's PR generator, so that I could create new databases based on the main environment, and then have them be torn down automatically by deleting the custom resource.
Describe the solution you'd like
I'd like the ACK for RDS to better support RestoreDBClusterToPointInTime
CC @aws-controllers-k8s/rds-maintainer could someone please take a look here and determine the complexity of implementing this?
My work organization could be open to contributing the work if some initial guidance could be provided?
My work organization could be open to contributing the work if some initial guidance could be provided?
@abatilo we are always available to help. :) Hop onto the Kubernetes Slack community #aws-controllers-k8s channel. That's the best way to get into design discussions. Myself and @brucegucode can assist you in planning this feature out.
I would also point out a previous PR in the rds-controller repository that might be useful as reference: https://github.com/aws-controllers-k8s/rds-controller/pull/101
aws-controllers-k8s/rds-controller#101 lets you restore a database fully from snapshot, but it does not let you select the point-in-time. Here is a walkthrough on how to do that.
To go to an exact point-in-time, you would need:
RestoreDBClusterToPointInTime(for Aurora)RestoreDBInstanceToPointInTime(for all other engines)
There are definitely a bunch of use cases for the above -- I've seen the need for this from Kubernetes and have done similar things myself :smile:
@abatilo For your specific use case, is there a need to restore to a specific point in time or does restoring from the last snapshot work?
For my use case, restoring to latest with specifically Aurora Postgres is all I'm looking to do at the moment @jkatz.
Thank you for the reference PRs. I don't want to say we're committing to anything just yet but those are some great starting points!
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle rotten
Rotten issues close after 60d of inactivity.
Reopen the issue with /reopen.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/close
@ack-bot: Closing this issue.
In response to this:
Rotten issues close after 60d of inactivity. Reopen the issue with
/reopen. Provide feedback via https://github.com/aws-controllers-k8s/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
![ack-prow[bot] avatar](https://avatars.githubusercontent.com/in/260409?v=4 "Published by a pub.dev verified publisher"){kind=small}
Rotten issues close after 60d of inactivity.
Reopen the issue with /reopen.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/close
@ack-bot: Closing this issue.
In response to this:
Rotten issues close after 60d of inactivity. Reopen the issue with
/reopen. Provide feedback via https://github.com/aws-controllers-k8s/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Rotten issues close after 60d of inactivity.
Reopen the issue with /reopen.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/close
@ack-bot: Closing this issue.
In response to this:
Rotten issues close after 60d of inactivity. Reopen the issue with
/reopen. Provide feedback via https://github.com/aws-controllers-k8s/community. /close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.