#velero — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #velero, aggregated by home.social.
-
https://www.europesays.com/es/733989/ Así celebró Amaia Montero los 50 con sus compañeros de La Oreja de Van Gogh: un «perfecto» día en velero y cita gastronómica en Usurbil #amaia #Celebrities #celebro #cita #companeros #dia #Entertainment #Entretenimiento #ES #España #Famosos #gastronómica #gogh #montero #oreja #perfecto #Spain #usurbil #van #velero
-
Semar rescata a nueve personas de velero en Topolobampo
La Secretaría de Marina rescató a nueve personas, entre ellas dos menores, que viajaban en un velero afectado por condiciones meteorológicas adversas frente a Topolobampo, Sinaloa.
Por Martín García | Reportero
Nueve personas, entre ellas dos menores de edad, fueron rescatadas por personal de la Secretaría de Marina – Armada de México (Semar) luego de que el velero en el que navegaban quedara en situación de riesgo debido a las condiciones meteorológicas adversas frente a Topolobampo, Sinaloa.
La operación fue realizada por elementos de la Estación Naval de Búsqueda, Rescate y Vigilancia Marítima (Ensar) Topolobampo, quienes atendieron un reporte de auxilio en el que se alertó que la embarcación requería apoyo para salvaguardar la integridad de sus tripulantes.
De acuerdo con la dependencia, la embarcación transportaba a siete personas adultas y dos menores de edad, por lo que se ordenó el zarpe inmediato de una unidad de rescate para brindar asistencia.
Personal naval trasladó a los tripulantes a un lugar seguro
Al arribar al sitio del incidente, el personal naval localizó el velero y efectuó el desembarque seguro de sus nueve ocupantes, quienes fueron trasladados a las instalaciones navales de Topolobampo.
En el muelle, personal de Sanidad Naval realizó una valoración médica a los tripulantes y determinó que todos se encontraban en buenas condiciones de salud, por lo que posteriormente se retiraron por sus propios medios.
También aseguraron el velero
Una vez concluido el rescate de los ocupantes, elementos de la Armada regresaron al lugar donde permanecía la embarcación para brindarle apoyo durante la navegación.
El velero fue conducido mediante navegación en conserva hasta el Muelle Mingo, en Topolobampo, donde quedó resguardado de forma segura. –sn–
Sociedad Noticias¡Conéctate con Sociedad Noticias! Suscríbete a nuestro canal de YouTube y activa las notificaciones, o bien, síguenos en las redes sociales: Facebook, Twitter e Instagram.
También, te invitamos a que te sumes a nuestro canal de información en tiempo real a través de Telegram.
#NoticiasMX #PeriodismoParaTi #PeriodismoParaTiSociedadNoticias #ArmadaDeMéxico #Cdmx #ENSARTopolobampo #GuardiaCostera #Información #InformaciónMéxico #México #Morena #noticia #noticias #NoticiasMéxico #NoticiasSociedad #rescateMarítimo #SecretaríaDeMarina #Semar #Sinaloa #SN #Sociedad #SociedadNoticias #SociedadNoticiasCom #sociedadNoticias #SociedadNoticiasCom #Topolobampo #velero -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.
RE: https://sakurajima.social/notes/alt7i6brp4 -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn
#kubernetes #homelab -
https://www.europesays.com/es/526169/ GRAN ACUARELA | El gran velero encallado en Xàbia ya es arte: «Resulta hipnótico» #acuarela #arte #ArteYDiseño #Arts #ArtsAndDesign #BauBau #Design #Diseño #encallado #Entertainment #Entretenimiento #ES #España #Fotografía #gran #LaMarina #mar #Spain #temporales #TIERRA #velero #xàbia
-
Very excited to have gotten through a pretty big lift + refactor in the #homelab over the last few weeks. For a while, I’ve had one foot in my old, disorganized, scattered Docker services, and one foot in a new, fully automated, #gitops pseudo-prod for home.
Well, no more. I’ve cleaned up all of the old shit. Centralized config, linted, backed up, refactored, and smoke tested the core platform. It completely spins up and down, with one Playbook, data fully backed up, etc.
Hardware:
- 3x #amd mini PC’s w/32GB RAM
- #synology DS1813+
- 1x Intel miniPC for #homeassistant OS
- TP-Link #Omada gateway, PoE switch, and AP’sMy core stack is, going from hardware to workload lifecycle and access:
- #proxmox
- #fedora #fedora_coreos VM’s
- #k3s #Rancher #kubernetes
- #nfs subdir provisioner
- #ansible
- #argocd
- #Tailscale
- #1password Kubernetes Operator
- #veleroI just did a DR drill with my kids’ #minecraft servers, and it worked great, and I’m super pumped with #selfhosting #paperlessngx!
Those are the first family-facing apps that I’ve deployed, and I’ve got a laundry list of more services on the way.
It was far, far more work than it probably needed to be…but I also can fully trust it with our most important personal docs, which was priority one.
-
Very excited to have gotten through a pretty big lift + refactor in the #homelab over the last few weeks. For a while, I’ve had one foot in my old, disorganized, scattered Docker services, and one foot in a new, fully automated, #gitops pseudo-prod for home.
Well, no more. I’ve cleaned up all of the old shit. Centralized config, linted, backed up, refactored, and smoke tested the core platform. It completely spins up and down, with one Playbook, data fully backed up, etc.
Hardware:
- 3x #amd mini PC’s w/32GB RAM
- #synology DS1813+
- 1x Intel miniPC for #homeassistant OS
- TP-Link #Omada gateway, PoE switch, and AP’sMy core stack is, going from hardware to workload lifecycle and access:
- #proxmox
- #fedora #fedora_coreos VM’s
- #k3s #Rancher #kubernetes
- #nfs subdir provisioner
- #ansible
- #argocd
- #Tailscale
- #1password Kubernetes Operator
- #veleroI just did a DR drill with my kids’ #minecraft servers, and it worked great, and I’m super pumped with #selfhosting #paperlessngx!
Those are the first family-facing apps that I’ve deployed, and I’ve got a laundry list of more services on the way.
It was far, far more work than it probably needed to be…but I also can fully trust it with our most important personal docs, which was priority one.
-
Very excited to have gotten through a pretty big lift + refactor in the #homelab over the last few weeks. For a while, I’ve had one foot in my old, disorganized, scattered Docker services, and one foot in a new, fully automated, #gitops pseudo-prod for home.
Well, no more. I’ve cleaned up all of the old shit. Centralized config, linted, backed up, refactored, and smoke tested the core platform. It completely spins up and down, with one Playbook, data fully backed up, etc.
Hardware:
- 3x #amd mini PC’s w/32GB RAM
- #synology DS1813+
- 1x Intel miniPC for #homeassistant OS
- TP-Link #Omada gateway, PoE switch, and AP’sMy core stack is, going from hardware to workload lifecycle and access:
- #proxmox
- #fedora #fedora_coreos VM’s
- #k3s #Rancher #kubernetes
- #nfs subdir provisioner
- #ansible
- #argocd
- #Tailscale
- #1password Kubernetes Operator
- #veleroI just did a DR drill with my kids’ #minecraft servers, and it worked great, and I’m super pumped with #selfhosting #paperlessngx!
Those are the first family-facing apps that I’ve deployed, and I’ve got a laundry list of more services on the way.
It was far, far more work than it probably needed to be…but I also can fully trust it with our most important personal docs, which was priority one.
-
Very excited to have gotten through a pretty big lift + refactor in the #homelab over the last few weeks. For a while, I’ve had one foot in my old, disorganized, scattered Docker services, and one foot in a new, fully automated, #gitops pseudo-prod for home.
Well, no more. I’ve cleaned up all of the old shit. Centralized config, linted, backed up, refactored, and smoke tested the core platform. It completely spins up and down, with one Playbook, data fully backed up, etc.
Hardware:
- 3x #amd mini PC’s w/32GB RAM
- #synology DS1813+
- 1x Intel miniPC for #homeassistant OS
- TP-Link #Omada gateway, PoE switch, and AP’sMy core stack is, going from hardware to workload lifecycle and access:
- #proxmox
- #fedora #fedora_coreos VM’s
- #k3s #Rancher #kubernetes
- #nfs subdir provisioner
- #ansible
- #argocd
- #Tailscale
- #1password Kubernetes Operator
- #veleroI just did a DR drill with my kids’ #minecraft servers, and it worked great, and I’m super pumped with #selfhosting #paperlessngx!
Those are the first family-facing apps that I’ve deployed, and I’ve got a laundry list of more services on the way.
It was far, far more work than it probably needed to be…but I also can fully trust it with our most important personal docs, which was priority one.
-
Very excited to have gotten through a pretty big lift + refactor in the #homelab over the last few weeks. For a while, I’ve had one foot in my old, disorganized, scattered Docker services, and one foot in a new, fully automated, #gitops pseudo-prod for home.
Well, no more. I’ve cleaned up all of the old shit. Centralized config, linted, backed up, refactored, and smoke tested the core platform. It completely spins up and down, with one Playbook, data fully backed up, etc.
Hardware:
- 3x #amd mini PC’s w/32GB RAM
- #synology DS1813+
- 1x Intel miniPC for #homeassistant OS
- TP-Link #Omada gateway, PoE switch, and AP’sMy core stack is, going from hardware to workload lifecycle and access:
- #proxmox
- #fedora #fedora_coreos VM’s
- #k3s #Rancher #kubernetes
- #nfs subdir provisioner
- #ansible
- #argocd
- #Tailscale
- #1password Kubernetes Operator
- #veleroI just did a DR drill with my kids’ #minecraft servers, and it worked great, and I’m super pumped with #selfhosting #paperlessngx!
Those are the first family-facing apps that I’ve deployed, and I’ve got a laundry list of more services on the way.
It was far, far more work than it probably needed to be…but I also can fully trust it with our most important personal docs, which was priority one.
-
Having recently experienced a rather horrible #Kubernetes crash, I'm looking for #backup solutions. We're good with PostgreSQL since we're using #CNPG with remote transaction logs to an offsite #S3 bucket. I need something for volumes and maybe Kubernetes resources. #Longhorn offers S3 backups for it's own volumes, but for other #CSI like local #OpenEBS, maybe #Velero? Thoughts?
-
Having recently experienced a rather horrible #Kubernetes crash, I'm looking for #backup solutions. We're good with PostgreSQL since we're using #CNPG with remote transaction logs to an offsite #S3 bucket. I need something for volumes and maybe Kubernetes resources. #Longhorn offers S3 backups for it's own volumes, but for other #CSI like local #OpenEBS, maybe #Velero? Thoughts?
-
Having recently experienced a rather horrible #Kubernetes crash, I'm looking for #backup solutions. We're good with PostgreSQL since we're using #CNPG with remote transaction logs to an offsite #S3 bucket. I need something for volumes and maybe Kubernetes resources. #Longhorn offers S3 backups for it's own volumes, but for other #CSI like local #OpenEBS, maybe #Velero? Thoughts?
-
Having recently experienced a rather horrible #Kubernetes crash, I'm looking for #backup solutions. We're good with PostgreSQL since we're using #CNPG with remote transaction logs to an offsite #S3 bucket. I need something for volumes and maybe Kubernetes resources. #Longhorn offers S3 backups for it's own volumes, but for other #CSI like local #OpenEBS, maybe #Velero? Thoughts?
-
Having recently experienced a rather horrible #Kubernetes crash, I'm looking for #backup solutions. We're good with PostgreSQL since we're using #CNPG with remote transaction logs to an offsite #S3 bucket. I need something for volumes and maybe Kubernetes resources. #Longhorn offers S3 backups for it's own volumes, but for other #CSI like local #OpenEBS, maybe #Velero? Thoughts?
-
Homelab project idea: Standby disaster recovery/Continuity of Operations node
The parent's fileserver (PFS) will be running Proxmox, and will have plenty of headroom. The idea is to run a simple single-node cluster in a VM (likely Talos) and configure Velero to do a restore of critical applications to this single-node cluster.
I'm not sure how to handle storage classes. The DR node won't have Ceph, I'm thinking maybe configuring a local storage provisioner and making fake storage classes (i.e. a "cephfs" storage class that lies and points to a local disk).
Cilium/CNI would be configured in a much more basic manner as well maybe I could also do the fake thing and map the "cilium" ingress to something else, or just configure it in L2 mode. All I would need to do is switch some DNS records and I'd have only lost changes since the last backup.
The first victory would be a proof of concept but it might be possible to have a daily task that overwrites the DR cluster with the most recent successful backup.
Since the home automation and media streaming/acquisition apps won't be set to run on the DR node, a so goes reasonably sized VM should be able to handle things with no problem.
This would also put me at ease that if needed I could move my self-hosted platform to an event smaller significantly more portable/lower power physical machine, maybe even a single odroid H4 with 2-4 disks
#Kubernetes #Homelab #Velero #Backups #Selfhosted -
Homelab project idea: Standby disaster recovery/Continuity of Operations node
The parent's fileserver (PFS) will be running Proxmox, and will have plenty of headroom. The idea is to run a simple single-node cluster in a VM (likely Talos) and configure Velero to do a restore of critical applications to this single-node cluster.
I'm not sure how to handle storage classes. The DR node won't have Ceph, I'm thinking maybe configuring a local storage provisioner and making fake storage classes (i.e. a "cephfs" storage class that lies and points to a local disk).
Cilium/CNI would be configured in a much more basic manner as well maybe I could also do the fake thing and map the "cilium" ingress to something else, or just configure it in L2 mode. All I would need to do is switch some DNS records and I'd have only lost changes since the last backup.
The first victory would be a proof of concept but it might be possible to have a daily task that overwrites the DR cluster with the most recent successful backup.
Since the home automation and media streaming/acquisition apps won't be set to run on the DR node, a so goes reasonably sized VM should be able to handle things with no problem.
This would also put me at ease that if needed I could move my self-hosted platform to an event smaller significantly more portable/lower power physical machine, maybe even a single odroid H4 with 2-4 disks
#Kubernetes #Homelab #Velero #Backups #Selfhosted -
Homelab project idea: Standby disaster recovery/Continuity of Operations node
The parent's fileserver (PFS) will be running Proxmox, and will have plenty of headroom. The idea is to run a simple single-node cluster in a VM (likely Talos) and configure Velero to do a restore of critical applications to this single-node cluster.
I'm not sure how to handle storage classes. The DR node won't have Ceph, I'm thinking maybe configuring a local storage provisioner and making fake storage classes (i.e. a "cephfs" storage class that lies and points to a local disk).
Cilium/CNI would be configured in a much more basic manner as well maybe I could also do the fake thing and map the "cilium" ingress to something else, or just configure it in L2 mode. All I would need to do is switch some DNS records and I'd have only lost changes since the last backup.
The first victory would be a proof of concept but it might be possible to have a daily task that overwrites the DR cluster with the most recent successful backup.
Since the home automation and media streaming/acquisition apps won't be set to run on the DR node, a so goes reasonably sized VM should be able to handle things with no problem.
This would also put me at ease that if needed I could move my self-hosted platform to an event smaller significantly more portable/lower power physical machine, maybe even a single odroid H4 with 2-4 disks
#Kubernetes #Homelab #Velero #Backups #Selfhosted -
Homelab project idea: Standby disaster recovery/Continuity of Operations node
The parent's fileserver (PFS) will be running Proxmox, and will have plenty of headroom. The idea is to run a simple single-node cluster in a VM (likely Talos) and configure Velero to do a restore of critical applications to this single-node cluster.
I'm not sure how to handle storage classes. The DR node won't have Ceph, I'm thinking maybe configuring a local storage provisioner and making fake storage classes (i.e. a "cephfs" storage class that lies and points to a local disk).
Cilium/CNI would be configured in a much more basic manner as well maybe I could also do the fake thing and map the "cilium" ingress to something else, or just configure it in L2 mode. All I would need to do is switch some DNS records and I'd have only lost changes since the last backup.
The first victory would be a proof of concept but it might be possible to have a daily task that overwrites the DR cluster with the most recent successful backup.
Since the home automation and media streaming/acquisition apps won't be set to run on the DR node, a so goes reasonably sized VM should be able to handle things with no problem.
This would also put me at ease that if needed I could move my self-hosted platform to an event smaller significantly more portable/lower power physical machine, maybe even a single odroid H4 with 2-4 disks
#Kubernetes #Homelab #Velero #Backups #Selfhosted -
Homelab project idea: Standby disaster recovery/Continuity of Operations node
The parent's fileserver (PFS) will be running Proxmox, and will have plenty of headroom. The idea is to run a simple single-node cluster in a VM (likely Talos) and configure Velero to do a restore of critical applications to this single-node cluster.
I'm not sure how to handle storage classes. The DR node won't have Ceph, I'm thinking maybe configuring a local storage provisioner and making fake storage classes (i.e. a "cephfs" storage class that lies and points to a local disk).
Cilium/CNI would be configured in a much more basic manner as well maybe I could also do the fake thing and map the "cilium" ingress to something else, or just configure it in L2 mode. All I would need to do is switch some DNS records and I'd have only lost changes since the last backup.
The first victory would be a proof of concept but it might be possible to have a daily task that overwrites the DR cluster with the most recent successful backup.
Since the home automation and media streaming/acquisition apps won't be set to run on the DR node, a so goes reasonably sized VM should be able to handle things with no problem.
This would also put me at ease that if needed I could move my self-hosted platform to an event smaller significantly more portable/lower power physical machine, maybe even a single odroid H4 with 2-4 disks
#Kubernetes #Homelab #Velero #Backups #Selfhosted -
I was remembered, that behind velero backup Broadcom is. Time to ditch velero before Broadcom does Broadcom things and test Volsync for backups.
-
I was remembered, that behind velero backup Broadcom is. Time to ditch velero before Broadcom does Broadcom things and test Volsync for backups.
-
I was remembered, that behind velero backup Broadcom is. Time to ditch velero before Broadcom does Broadcom things and test Volsync for backups.
-
I was remembered, that behind velero backup Broadcom is. Time to ditch velero before Broadcom does Broadcom things and test Volsync for backups.
-
The Velero backups are working except for the CephFS volumes :neocat_sob:
I have no idea why it just throws timeout errors but I can create a manual snapshot which doesn't take that long?
I'm so close to getting past this step but I'm not exactly where to look next
#Kubernetes #Velero #Ceph #Backups -
The Velero backups are working except for the CephFS volumes :neocat_sob:
I have no idea why it just throws timeout errors but I can create a manual snapshot which doesn't take that long?
I'm so close to getting past this step but I'm not exactly where to look next
#Kubernetes #Velero #Ceph #Backups -
The Velero backups are working except for the CephFS volumes :neocat_sob:
I have no idea why it just throws timeout errors but I can create a manual snapshot which doesn't take that long?
I'm so close to getting past this step but I'm not exactly where to look next
#Kubernetes #Velero #Ceph #Backups -
The Velero backups are working except for the CephFS volumes :neocat_sob:
I have no idea why it just throws timeout errors but I can create a manual snapshot which doesn't take that long?
I'm so close to getting past this step but I'm not exactly where to look next
#Kubernetes #Velero #Ceph #Backups -
The Velero backups are working except for the CephFS volumes :neocat_sob:
I have no idea why it just throws timeout errors but I can create a manual snapshot which doesn't take that long?
I'm so close to getting past this step but I'm not exactly where to look next
#Kubernetes #Velero #Ceph #Backups -
I'm very disappointed in you #Velero.
You can't restore your own snapshots USING DEFAULT SETTINGS.
Like data is in the bucket, you restore the CRs, but not the volumes?
-
I'm very disappointed in you #Velero.
You can't restore your own snapshots USING DEFAULT SETTINGS.
Like data is in the bucket, you restore the CRs, but not the volumes?
-
I'm very disappointed in you #Velero.
You can't restore your own snapshots USING DEFAULT SETTINGS.
Like data is in the bucket, you restore the CRs, but not the volumes?
-
I'm very disappointed in you #Velero.
You can't restore your own snapshots USING DEFAULT SETTINGS.
Like data is in the bucket, you restore the CRs, but not the volumes?
-
I'm very disappointed in you #Velero.
You can't restore your own snapshots USING DEFAULT SETTINGS.
Like data is in the bucket, you restore the CRs, but not the volumes?
-
the #velero adventure continued. my config in my cluster was good enough for things to run buuuut
- this is necessary to work with backblaze b2 https://github.com/vmware-tanzu/velero/issues/7534
- velero node agent is a thing which i hadn't needed to enable before (or went by a different value in a previous version and i'd removed it.. i think thats what happened) https://github.com/vmware-tanzu/helm-charts/blob/fcc60b0ca3886eb760151c69c166108a807efdef/charts/velero/values.yaml#L535apparently my backups haven't been working for a very, very long time! 😅
-
the #velero adventure continued. my config in my cluster was good enough for things to run buuuut
- this is necessary to work with backblaze b2 https://github.com/vmware-tanzu/velero/issues/7534
- velero node agent is a thing which i hadn't needed to enable before (or went by a different value in a previous version and i'd removed it.. i think thats what happened) https://github.com/vmware-tanzu/helm-charts/blob/fcc60b0ca3886eb760151c69c166108a807efdef/charts/velero/values.yaml#L535apparently my backups haven't been working for a very, very long time! 😅
-
the #velero adventure continued. my config in my cluster was good enough for things to run buuuut
- this is necessary to work with backblaze b2 https://github.com/vmware-tanzu/velero/issues/7534
- velero node agent is a thing which i hadn't needed to enable before (or went by a different value in a previous version and i'd removed it.. i think thats what happened) https://github.com/vmware-tanzu/helm-charts/blob/fcc60b0ca3886eb760151c69c166108a807efdef/charts/velero/values.yaml#L535apparently my backups haven't been working for a very, very long time! 😅
-
the #velero adventure continued. my config in my cluster was good enough for things to run buuuut
- this is necessary to work with backblaze b2 https://github.com/vmware-tanzu/velero/issues/7534
- velero node agent is a thing which i hadn't needed to enable before (or went by a different value in a previous version and i'd removed it.. i think thats what happened) https://github.com/vmware-tanzu/helm-charts/blob/fcc60b0ca3886eb760151c69c166108a807efdef/charts/velero/values.yaml#L535apparently my backups haven't been working for a very, very long time! 😅
-
the #velero adventure continued. my config in my cluster was good enough for things to run buuuut
- this is necessary to work with backblaze b2 https://github.com/vmware-tanzu/velero/issues/7534
- velero node agent is a thing which i hadn't needed to enable before (or went by a different value in a previous version and i'd removed it.. i think thats what happened) https://github.com/vmware-tanzu/helm-charts/blob/fcc60b0ca3886eb760151c69c166108a807efdef/charts/velero/values.yaml#L535apparently my backups haven't been working for a very, very long time! 😅
-
#velero tweaks done!!!!!
split out config into the relevant CRDs like the error suggested, and tweaked the values so the included resources arent stepping on my identically named bespoke resources. THAT WASNT SO BAD
https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml
note to self: things work when you slow down, read, get more slower, read again...
-
#velero tweaks done!!!!!
split out config into the relevant CRDs like the error suggested, and tweaked the values so the included resources arent stepping on my identically named bespoke resources. THAT WASNT SO BAD
https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml
note to self: things work when you slow down, read, get more slower, read again...
-
#velero tweaks done!!!!!
split out config into the relevant CRDs like the error suggested, and tweaked the values so the included resources arent stepping on my identically named bespoke resources. THAT WASNT SO BAD
https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml
note to self: things work when you slow down, read, get more slower, read again...
-
#velero tweaks done!!!!!
split out config into the relevant CRDs like the error suggested, and tweaked the values so the included resources arent stepping on my identically named bespoke resources. THAT WASNT SO BAD
https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml
note to self: things work when you slow down, read, get more slower, read again...
-
#velero tweaks done!!!!!
split out config into the relevant CRDs like the error suggested, and tweaked the values so the included resources arent stepping on my identically named bespoke resources. THAT WASNT SO BAD
https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/values.yaml
note to self: things work when you slow down, read, get more slower, read again...
-
#homelab housekeeping:
- updated all my #helm charts (except #velero)
- migrated #postgresql from previous major version to current major version
- everything still works
- feeling good about doing a hobby ive neglected for far too long#todo #wordpress layout adjustments, get matrix #synapse working again and REALLY RESEARCH proper synapse database housekeeping tasks so things dont get out of control like they always do
happy friday yall 🎉
-
#homelab housekeeping:
- updated all my #helm charts (except #velero)
- migrated #postgresql from previous major version to current major version
- everything still works
- feeling good about doing a hobby ive neglected for far too long#todo #wordpress layout adjustments, get matrix #synapse working again and REALLY RESEARCH proper synapse database housekeeping tasks so things dont get out of control like they always do
happy friday yall 🎉
-
#homelab housekeeping:
- updated all my #helm charts (except #velero)
- migrated #postgresql from previous major version to current major version
- everything still works
- feeling good about doing a hobby ive neglected for far too long#todo #wordpress layout adjustments, get matrix #synapse working again and REALLY RESEARCH proper synapse database housekeeping tasks so things dont get out of control like they always do
happy friday yall 🎉
-
#homelab housekeeping:
- updated all my #helm charts (except #velero)
- migrated #postgresql from previous major version to current major version
- everything still works
- feeling good about doing a hobby ive neglected for far too long#todo #wordpress layout adjustments, get matrix #synapse working again and REALLY RESEARCH proper synapse database housekeeping tasks so things dont get out of control like they always do
happy friday yall 🎉
-
#homelab housekeeping:
- updated all my #helm charts (except #velero)
- migrated #postgresql from previous major version to current major version
- everything still works
- feeling good about doing a hobby ive neglected for far too long#todo #wordpress layout adjustments, get matrix #synapse working again and REALLY RESEARCH proper synapse database housekeeping tasks so things dont get out of control like they always do
happy friday yall 🎉
