-
Notifications
You must be signed in to change notification settings - Fork 379
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
Update spilo image to resolve some vulnerabilities #965
Comments
The following comment might be the reason why it hasn't been updated for a while: |
There has actually been a It is true however that it would be better to have more frequent releases of the image. Seeing how they are built, even based on the same commit that would be enough to expose and distribute fixes for the applications and tools that are included in the image. |
To save people who are using the postgres-operator from some headaches, do not run 3.1-p1 with the latest released version of the operator. In that image, the patroni version, introduced changes which makes failover iffy. |
|
The last official release of the spilo image is already more than 10 months old:
https://github.com/zalando/spilo/releases/tag/3.0-p1
Are there any plans to update the spilo image in order to reduce some of the vulnerabilities that are caused by the installed packages and their age?
The text was updated successfully, but these errors were encountered: