-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
PersistentVolume with external storage support for in-cluster databases #1231
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
mathieu-benoit
changed the title
Nov 3, 2022
redis
as a StatefulSet
with PersistenVolume
redis
as a StatefulSet
with PersistentVolume
NimJay
added
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
priority: p3
Desirable enhancement or fix. May not be included in next release.
labels
Nov 4, 2022
This is a great idea, and a good point of collaboration for myself and the GKE DPEs. My initial thoughts:
|
Linking the analogue for Bank of Anthos: GoogleCloudPlatform/bank-of-anthos#1068 |
bourgeoisor
changed the title
PersistentVolume with external storage support for in-cluster databases
May 3, 2023
redis
as a StatefulSet
with PersistentVolume
Commenting since this is near out-of-SLO:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Today, the in-cluster
redis
database is aDeployment
, as a best practice for such in-cluster scenario it would be great to have it asStatefulSet
with aPersistentVolume
. Maybe with Filestore like illustrated here? Or maybe another storage? That will also illustrate yet another great story with multiple Google Cloud services while showing best practices. This will allow Online Boutique's users (Googlers, etc.) to have a ready to use solution for such stateful workloads scenarios.We maybe don't want to have this as default, and we may want to keep this as
Deployment
by default (?), but maybe to start with a new Online Boutique variation (i.e. Kustomize overlay) would be a great candidate?Tagging @bourgeoisor @ahrarmonsur @charlieyu1996 as I'm sure they could provide more insights around this and maybe planning this for 2023?
The text was updated successfully, but these errors were encountered: