Please update docker image to last version on DockerHub

[rabb1t]

Hi,

Is there any plans to include the fix of CVE-2020-10715 into the docker hub image?
As far as I can see the image build is still from Oct-2018:

$ docker image inspect -f  {{.Created}} openshift/origin-web-console:v3.11.0
2018-10-19T04:43:16.030048426Z

Thank you!

[spadgett]

Hi, unfortunately no one in the community is producing OKD 3 builds. I'd encourage you to move to OKD 4 if possible. See this email for more background:

http://lists.openshift.redhat.com/openshift-archives/users/2021-January/msg00006.html

It is possible for you to build a new console image using the instructions here:

https://github.com/openshift/origin-web-console-server/#building

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.