[WIP] CONSOLE-4277: Console-operator should make use of the new downloads server

[Mylanos]

Prepare the console-operator for new downloads server image, to be built from the openshift/console codebase (link) as part of release repository as soon the CONSOLE-4276 merges.

Setup the configuration of the artifacts to be stored in the ConfigMap as part of the CO repo and use it instead of the default artifactsConfiguration provided in console.

Tested it on my own image of the downloads-server instead of the image TO BE published in the release repo. At the moment I left the original image in place - Needs to be updated when CONSOLE-4276 merges.

On the following screenshot we can see the downloads-server pod running.

Showcase of the pod being deployed with updated downloads-deployment, and artifacts download links.
https://github.com/user-attachments/assets/1fc9e023-32fa-4b38-8802-3599160ce4cd

[openshift-ci-robot]

@Mylanos: This pull request references CONSOLE-4277 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Prepare the console-operator for new downloads server image, to be built from the openshift/console codebase (link) an published as part of release repository as soon the CONSOLE-4276 merges.

Introduce the configuration of the artifacts to be stored in the ConfigMapas part of the CO repo and use it instead of the defaulyartifactsConfiguration` provided in console.

Tested it on my own image of the downloads-server, built from openshift/console instead of the image TO BE published in the release repo. At the moment I left the original images in place - Needs to be updated when CONSOLE-4276 merges.

On the following screenshot we can see the downloads-server pod running.

Showcase of the pod being deployed with updated downloads-deployment, and artifacts download links.
https://github.com/user-attachments/assets/1fc9e023-32fa-4b38-8802-3599160ce4cd

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@Mylanos: This pull request references CONSOLE-4277 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Prepare the console-operator for new downloads server image, to be built from the openshift/console codebase (link) an published as part of release repository as soon the CONSOLE-4276 merges.

Introduce the configuration of the artifacts to be stored in the ConfigMap as part of the CO repo and use it instead of the defauly artifactsConfiguration provided in console.

Tested it on my own image of the downloads-server, built from openshift/console instead of the image TO BE published in the release repo. At the moment I left the original images in place - Needs to be updated when CONSOLE-4276 merges.

On the following screenshot we can see the downloads-server pod running.

Showcase of the pod being deployed with updated downloads-deployment, and artifacts download links.
https://github.com/user-attachments/assets/1fc9e023-32fa-4b38-8802-3599160ce4cd

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Mylanos
Once this PR has been reviewed and has the lgtm label, please assign therealjon for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@Mylanos: This pull request references CONSOLE-4277 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Prepare the console-operator for new downloads server image, to be built from the openshift/console codebase (link) as part of release repository as soon the CONSOLE-4276 merges.

Setup the configuration of the artifacts to be stored in the ConfigMap as part of the CO repo and use it instead of the default artifactsConfiguration provided in console.

Tested it on my own image of the downloads-server instead of the image TO BE published in the release repo. At the moment I left the original image in place - Needs to be updated when CONSOLE-4276 merges.

On the following screenshot we can see the downloads-server pod running.

Showcase of the pod being deployed with updated downloads-deployment, and artifacts download links.
https://github.com/user-attachments/assets/1fc9e023-32fa-4b38-8802-3599160ce4cd

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@Mylanos: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-ovn	1eba0c8	link	true	/test e2e-gcp-ovn
ci/prow/e2e-aws-ovn-single-node	1eba0c8	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-azure-ovn-upgrade	1eba0c8	link	true	/test e2e-azure-ovn-upgrade

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.