feat(KFLUXUI-504): Add banner content yaml and its kustomization files

[testcara]

KFLUXUI-500 aims to provide konflux banner to users.

The PR does:
supporting the single manual banner:

• add the banner-content.yaml for each cluster under konflux-info
• update its kustomize to ensure the its confimap could be generated
• add README.md and github workflow validation support for banner content including schema & safe content
  supporting the multiple auto generated alerts:
• add the auto-alerts directory and its fake kustomize
• update genearl kustomize for auto-alerts
• update README.md to explain how we can enjoy the auto-alerts.

Here is one video about how UI integrate with them:
https://drive.google.com/file/d/17X3qkgLD7aXWq_wnuteAWUu3WE7_J2M5/view

[gbenhaim]

Please move the content of https://github.com/testcara/konflux-banner into a directory in this repo (under the components directory)

Please deploy those configmap to the konflux-info namespace since its purpose is to store information which is accessible by all authenticated users.

Thanks !

[gbenhaim]

I really liked the implementation because it will also be possible to generate those confimaps with the banner details dynamically based on alerts.

I left a comment above about the way it should be deployed.

Thank you for working on this.

[gbenhaim]

I have a question, does each banner stored in its own configmap? I would like to also generate banners dynamically, it means that we would need the UI to read multiple configmaps with the banner details from the cluster.
Is it possible?

cc @sahil143

[testcara]

I have a question, does each banner stored in its own configmap? I would like to also generate banners dynamically, it means that we would need the UI to read multiple configmaps with the banner details from the cluster. Is it possible?

cc @sahil143

@gbenhaim Thank you for the review and quick response.

• does each banner stored in its own configmap -> yeah. it would be

• I would like to also generate banners dynamically -> based on the current design, users just need to submit one pure yaml PR manually to specify the banner content, see the example PR: https://github.com/testcara/konflux-banner/pull/5/files . Once the PR is merged. The corresponding configmap would be refreshed in real time. but it is also good to update the yaml by some automation. CI for the banner would test its schema and content to ensure the update is validate.

• it means that we would need the UI to read multiple configmaps with the banner details from the cluster. Is it possible?
  -> One cluster just have one banner configmap. so UI just fetch its own banner configmap then show its content.

[testcara]

Please move the content of https://github.com/testcara/konflux-banner into a directory in this repo (under the components directory)

Please deploy those configmap to the konflux-info namespace since its purpose is to store information which is accessible by all authenticated users.

Thanks !

@gbenhaim could you help to double-confirm whether i got your suggestion correctly?

• move the github.com/testcara/konflux-banner/ as konflux-banner-content component to infra-deplouments repo
• delete the testcara/konflux-banner repo
• update the konflux-banner component properly:
  • changing konflux-banner namespace to konflux-info
  • changing repoURL to the new one

Thank you for the great help. :-)

[gbenhaim]

Please move the content of https://github.com/testcara/konflux-banner into a directory in this repo (under the components directory)
Please deploy those configmap to the konflux-info namespace since its purpose is to store information which is accessible by all authenticated users.
Thanks !

@gbenhaim could you help to double-confirm whether i got your suggestion correctly?

• move the github.com/testcara/konflux-banner/ as konflux-banner-content component to infra-deplouments repo

You can use the existing konflux-info argo app and component folder, no need to create a new one.

• delete the testcara/konflux-banner repo

• update the konflux-banner component properly:

  • changing konflux-banner namespace to konflux-info
  • changing repoURL to the new one

Thank you for the great help. :-)

The rest is correct.

I would also want to get a change in the ui so it would know how to read multiple configmaps from the cluster. Dynically generated configmap would be creates using automation directly in the cluster and not using prs.

[testcara]

@gbenhaim hi, Gal, i refreshed the PR, could you help to review again? BTW, the description includes what the PR does or not covered, hope it makes the review a bit easier. Thank you for the help.

[testcara]

@gbenhaim i tried to support the two kinds of banners now, see the https://drive.google.com/file/d/17X3qkgLD7aXWq_wnuteAWUu3WE7_J2M5/view. looking forward to any feedback. thank you.

[gbenhaim]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gbenhaim, testcara

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [gbenhaim]

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

[testcara]

i would change the label to recommended way like 'app.kubernetes.io/name: my-app'