Skip to content
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

Migrate away from using Bitnami for dependencies in Helm chart. No support for arm64 containers. #25

Open
nodesocket opened this issue Mar 31, 2022 · 9 comments

Comments

@nodesocket
Copy link

nodesocket commented Mar 31, 2022

Pitch

The Helm chart Bitnami dependencies (PostgreSQL, Redis, ElastiCache) all don't support arm64 platform even though the Bitnami community has been asking for this support forever.

https://github.com/mastodon/mastodon/blob/ef196c913c77338be5ebb1e02af2f6225f857080/chart/Chart.yaml#L25-L36

Is it possible to migrate to another provider for these dependencies who maintain arm64 containers?

Motivation

Run Kubernetes cluster on arm64.

@dustinrue
Copy link

I actually would vote for removing dependencies entirely and require users install these items separately. How to do so could be documented but as it is currently implemented, this helm chart is reliant on common functionality provided by those charts. I feel like this binds the chart too tightly to these other charts. That said, there are a number of outstanding PR that are in progress and some of the issues I am seeing are resolved in those charts.

@nikdoof
Copy link

nikdoof commented Nov 16, 2022

To further @dustinrue's comment, further issues can occur when updating these dependencies, for example the PostgreSQL chart provides no automated solution for upgrading between major releases, leaving it to the user to manage the migration themselves. This could present a problem in the future, either of having the charts pinned at an old and potentially EOL version, or updating and causing users headaches for what they expected as a straight Mastodon upgrade.

@ineffyble ineffyble transferred this issue from mastodon/mastodon Dec 13, 2022
@deepy
Copy link
Contributor

deepy commented Dec 14, 2022

I've not tested redis personally yet, but the current functionality supports disabling all the bitnami charts

@magsol
Copy link

magsol commented Dec 14, 2022

I'm currently working on a series of (unofficial) blog posts detailing how I got Mastodon running by first disabling all the dependencies (redis, postgres, elasticsearch) and spinning them up separately. Would be happy to help transfer them over to official documentation, if that's an effort deemed worthy of some of the devs' time?

@slapula
Copy link

slapula commented Dec 18, 2022

This may be of interest to folks here: https://github.com/ZCube/bitnami-compat

I haven't given these images a shot yet but apparently they work. All of the charts referenced here are supported (redis, ES, postgres, etc). I'm going to test them myself in the next few days.

@magsol
Copy link

magsol commented Dec 18, 2022 via email

@renchap
Copy link
Member

renchap commented Feb 17, 2023

Hi there 👋

I am slowly going through the open PR and issues on this repo.

We are intending on splitting this chart in 2, one pure Mastodon chart, and a bigger "full stack" chart which will allow to (optionally) install the various dependencies to get a full Mastodon deployment in one go.

The new Mastodon chart should work well on ARM containers, and we will check what we can do for the fullstack one.

I am keeping this issue open for now, but will close it once we have one describing the change I just discussed above.

@carrodher
Copy link

Hi all, we are more than happy to announce that from now on the Bitnami container catalog is available as multi-arch in Docker Hub 🎉 🎉

Screenshot 2023-02-24 at 08 16 50

This means you don’t need to specify anything when pulling the container images from Docker Hub, Docker (or any other software) will automatically pull the container image matching the host platform from which the pull command was issued.

Here you can find more info about this announcement.

@magsol
Copy link

magsol commented Feb 28, 2023

Feel like this issue can probably be closed! Thanks @carrodher!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants