#rookceph — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #rookceph, aggregated by home.social.
-
I spent probably a weeks worth of hours learning more #kubernetes so I could save $60 a month.
I have a nice 3 node kube cluster with a 2 node #keepalived #haproxy TCP load balancer. All on #ARM VPS.
Haproxy ingress
#ExternalDNS operator
#CertManager
#RookCeph
#ArgoCD
#KeyCloak
#ValKey
#Mastodon
#CloudNativePG #Postgresql -
I spent probably a weeks worth of hours learning more #kubernetes so I could save $60 a month.
I have a nice 3 node kube cluster with a 2 node #keepalived #haproxy TCP load balancer. All on #ARM VPS.
Haproxy ingress
#ExternalDNS operator
#CertManager
#RookCeph
#ArgoCD
#KeyCloak
#ValKey
#Mastodon
#CloudNativePG #Postgresql -
I spent probably a weeks worth of hours learning more #kubernetes so I could save $60 a month.
I have a nice 3 node kube cluster with a 2 node #keepalived #haproxy TCP load balancer. All on #ARM VPS.
Haproxy ingress
#ExternalDNS operator
#CertManager
#RookCeph
#ArgoCD
#KeyCloak
#ValKey
#Mastodon
#CloudNativePG #Postgresql -
I spent probably a weeks worth of hours learning more #kubernetes so I could save $60 a month.
I have a nice 3 node kube cluster with a 2 node #keepalived #haproxy TCP load balancer. All on #ARM VPS.
Haproxy ingress
#ExternalDNS operator
#CertManager
#RookCeph
#ArgoCD
#KeyCloak
#ValKey
#Mastodon
#CloudNativePG #Postgresql -
It took a couple of weeks learning how the the values yaml files for rook ceph are supposed to be written. But I have finally managed to get a rook ceph storage cluster configured on a Talos kubernetes cluster!
I can do this stuff!
Next step is getting it to work with an ArgoCD CI/CD pipeline.
#HomeLab #Learning #Talos #Kubernetes #RookCeph #ArgoCD #Helm
-
It took a couple of weeks learning how the the values yaml files for rook ceph are supposed to be written. But I have finally managed to get a rook ceph storage cluster configured on a Talos kubernetes cluster!
I can do this stuff!
Next step is getting it to work with an ArgoCD CI/CD pipeline.
#HomeLab #Learning #Talos #Kubernetes #RookCeph #ArgoCD #Helm
-
It took a couple of weeks learning how the the values yaml files for rook ceph are supposed to be written. But I have finally managed to get a rook ceph storage cluster configured on a Talos kubernetes cluster!
I can do this stuff!
Next step is getting it to work with an ArgoCD CI/CD pipeline.
#HomeLab #Learning #Talos #Kubernetes #RookCeph #ArgoCD #Helm
-
It took a couple of weeks learning how the the values yaml files for rook ceph are supposed to be written. But I have finally managed to get a rook ceph storage cluster configured on a Talos kubernetes cluster!
I can do this stuff!
Next step is getting it to work with an ArgoCD CI/CD pipeline.
#HomeLab #Learning #Talos #Kubernetes #RookCeph #ArgoCD #Helm
-
It took a couple of weeks learning how the the values yaml files for rook ceph are supposed to be written. But I have finally managed to get a rook ceph storage cluster configured on a Talos kubernetes cluster!
I can do this stuff!
Next step is getting it to work with an ArgoCD CI/CD pipeline.
#HomeLab #Learning #Talos #Kubernetes #RookCeph #ArgoCD #Helm
-
This is what the new cluster looks like cabled up. Sexy, eh?
For the OS, I decided to go with RHEL 9.5. There are reasons. Red Hat really made some super dumb moves around CentOS Stream, but I don't think they are evil.
Setting up the routing for the ring topology network using #FRR seems to work. I'm getting about 26.6Gbit/sec across the Thunderbolt 4 interfaces. That is using ipv6. ipv4 is not quite working on those for me. And that is my blocker for #rookceph. -
This is what the new cluster looks like cabled up. Sexy, eh?
For the OS, I decided to go with RHEL 9.5. There are reasons. Red Hat really made some super dumb moves around CentOS Stream, but I don't think they are evil.
Setting up the routing for the ring topology network using #FRR seems to work. I'm getting about 26.6Gbit/sec across the Thunderbolt 4 interfaces. That is using ipv6. ipv4 is not quite working on those for me. And that is my blocker for #rookceph. -
Just had a brief blip in our S3 backend.
I swear, in the rook documents the first troubleshooting step should always be "Restart the operator because it probably silently shit itself"
-
Just had a brief blip in our S3 backend.
I swear, in the rook documents the first troubleshooting step should always be "Restart the operator because it probably silently shit itself"
-
Just had a brief blip in our S3 backend.
I swear, in the rook documents the first troubleshooting step should always be "Restart the operator because it probably silently shit itself"
-
Just had a brief blip in our S3 backend.
I swear, in the rook documents the first troubleshooting step should always be "Restart the operator because it probably silently shit itself"
-
Just had a brief blip in our S3 backend.
I swear, in the rook documents the first troubleshooting step should always be "Restart the operator because it probably silently shit itself"
-
TIL: The MicroK8s addon for "rook-ceph" is available since version 1.28.
Also, if you run `sudo snap install microk8s --classic`, it will install 1.27. 🙈 -
TIL: The MicroK8s addon for "rook-ceph" is available since version 1.28.
Also, if you run `sudo snap install microk8s --classic`, it will install 1.27. 🙈 -
TIL: The MicroK8s addon for "rook-ceph" is available since version 1.28.
Also, if you run `sudo snap install microk8s --classic`, it will install 1.27. 🙈
