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
CVE fixes needed #890
Comments
Yes, we should definitely work on this, unfortunately, the project has been abandoned for some months now. We are testing the current master branch state internally and if everything is fine, I hope to push the new release the next week (still without upgrading the Patroni version though) |
Hi what is the actual status? It would be really great to get an updated image (even without Patroni) asap. Best |
@hughcapet any new info? |
+1 any new info? |
I have attempted to use the current An issue has been created here: #923 |
Hello @hughcapet. Commenting you here
So does that mean that no one from zalando is supporting spilo image atm? |
The master branch is periodically updated and tested internally. The release cycle is unfortunately on hold now |
Any update here? |
I can not add anything to this now |
Understood. Are we safe to ensure the self build image is working properly by running the test routine located in the tests folder? Otherwise it would be nice to get some information about how you test that the image is working properly. I think once that is clear it should be easy to create a pipeline which builds images from the master branch. |
The test routine located in the tests folder indeed checks the main functionality blocks of Spilo (e.g. bootstrapping, in-place upgrades, cloning...). |
Hello,
when will be the next spilo release and will there be CVE fixes included? The current 3.0-p1 image has a lot of CVEs.
Would it be possible to have a regular / monthly release with updated base image packages to reduce CVEs in the future?
Best
Fabian
The text was updated successfully, but these errors were encountered: