Fix: Use legacy Bitnami registry for MySQL dependency to resolve CI failure#47
Conversation
|
PTAL @tananaev |
| mysql: | ||
| enabled: true | ||
| image: | ||
| repository: bitnamilegacy/mysql |
There was a problem hiding this comment.
Isn't this basically no longer supported?
There was a problem hiding this comment.
Yup.
But I don't know enough about mysql to fix this. I don't even use this feature of the chart (I use postgres).
My intention is to fix CI without breaking any users of mysql.
There was a problem hiding this comment.
I agree that we should focus on unblocking CI, but this doesn't seem like a good fix. This seems like a simpler hack and not a proper solution.
There was a problem hiding this comment.
The issue is that Bitnami removed all free versioned tags from their main repo, so the default chart is currently broken. https://www.reddit.com/r/kubernetes/comments/1mjx86p/comment/n7ep0il/
Two options to fix it:
- This PR (non-breaking): Use
bitnamilegacy. It's a workaround, but keeps the chart backward-compatible. IMO it is not a hack, just a badly maintained solution. - PR Fix: Replace bitnami/mysql with groundhog2k/mysql (official Docker image) #44: Replace the subchart with
groundhog2k/mysql(uses official MySQL image). This is cleaner long-term, but changes the configuration schema (breaking existing values).
If you want to fix this the proper way, let's merge #44 and ensure users know about the breaking change.
I still prefer we fix it with this workaround so users don't need to update their values. Keep in mind that nobody is updating the bitnami chart dependencies regularly in this repo anyways. So moving to a proper maintained helm chart doesn't really add much benefit...
|
Looks like it's failing. |
|
Fixed, PTAL |
2 participants
Fixes #42.
This PR updates the default MySQL image repository to
bitnamilegacy/mysqlto resolve theImagePullBackOfffailure in CI caused by Bitnami's repository restructuring (which moved version-pinned tags to a legacy namespace).This maintains compatibility for existing users without forcing a major version upgrade of MySQL.