-
Notifications
You must be signed in to change notification settings - Fork 344
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
Replace base image to ubi #767
Comments
+1 , although can you use |
+1 on using I would like to keep the scrip until ECL switches to golang based solution. |
Are they switching to golang at all? |
I don't think that will happen any time soon. |
@jpkrohling would like to work on this. If it is agreed to use ubi will start to work on this. |
I think there's nothing preventing us from using |
The current CentOS base image seems to have some vulnerabilities, according to Quay:
https://quay.io/repository/jaegertracing/jaeger-operator/manifest/sha256:0f33e0ea725448c52f74cb47a27391749868c888ad4a1f3d553c7bc31a8a28a7?tab=vulnerabilities
Changing the base image to
registry.access.redhat.com/ubi8/ubi
seems to be a valid fix:https://quay.io/repository/jpkroehling/jaeger-operator/manifest/sha256:e46a408f7496618b8923cf996dbad37d8b9c52b646eb0a97195ca01600f26226?tab=vulnerabilities
The
ubi-minimal
seems to be the default base image for new operators.@pavolloffay: we started using the
centos
image because of the TLS cert generation as part of the ES provisioning. I think we talked about replacing that with regular Go code, instead of relying on openssl. Do you still want to do that? If so, this change here could come after your change, so that we useubi-minimal
, which lacksdnf
. Otherwise, we could just useubi
instead.The text was updated successfully, but these errors were encountered: