Currently wishing I had a better way to manage multiple redis and minio storages

The minio operator is missing features that would streamline it (looked at rook a bit but I still can't justify it I think)

The redis operator basically doesn't exist, idk if a valkey one will happen. Maybe dragonflydb? Their docs seem not amazing for their operator tho

#kuberbetes #homelab
Huh there was a proposal for a native object storage framework but it doesn't look like it got traction:

https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support

edit: not dead yet! (
https://github.com/kubernetes/enhancements/issues/1979)
enhancements/keps/sig-storage/1979-object-storage-support at master · kubernetes/enhancements

Enhancements tracking repo for Kubernetes. Contribute to kubernetes/enhancements development by creating an account on GitHub.

GitHub
Oh no backend for on-prem ecept for ceph.... lmao at which point I could just run rook?

(
https://container-object-storage-interface.github.io/)
Kubernetes COSI | Kubernetes COSI

Description will go into a meta tag in <head />

@rachel Yupp, I also looked into this one briefly when setting up Rook, but went for Rook's own ObjectBucketClaim. I can't really recall why, but I think it was because COSI still felt a little bit too experimental?
@mmeier yeah not only experimental but turns out it doesn't even really do what I wanted it to do

Which was to feed it a regular persistent volume and have it serve objects from that

edit well it looks like it
could do that but not currently implemented just big3 clouds + ceph