Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on mastodon.keyboardvagabond.com

Moar adventures in #selfhosting for #keyboardvagabond! I think that I finally got the longhorn too-many-s3-calls networking issue resolved

Moar adventures in #selfhosting for #keyboardvagabond! I think that I finally got the longhorn too-many-s3-calls networking issue resolved https://blog.keyboardvagabond.com/michael-dileos-software-and-tech-blog/longhorns-backup-cost-savings-or-not-getting-surprise-bills

I also found that the #bitnami #helmchart for #harborRegistry didn't get updated with the latest migration they did, so I had to find out that they moved their repositories to bitnamilegacy and update my helm chart. That took a while to figure out why the image pulls failed!

@selfhosted
@selfhosting
#kubernetes

View original on mastodon.keyboardvagabond.com
4

2 replies

feddit.nl

Bitnami Helm charts are not maintained anymore. There are no updates for the charts and images in the legacy repository. Try to find a different chart for harbor registry and any other bitnami images and charts you use ASAP

1

You reached the end

Moar adventures in #selfhosting for #keyboardvagabond! I think that I finally got the longhorn too-many-s3-calls networking issue resolved | Spyke