Add README to elemetal-operator helm chart

[mjura]

No description provided.

[codecov-commenter]

Codecov Report

Merging #56 (46612a9) into main (2381ebc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   27.06%   27.06%           
=======================================
  Files           5        5           
  Lines         351      351           
=======================================
  Hits           95       95           
  Misses        250      250           
  Partials        6        6           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2381ebc...46612a9. Read the comment docs.

[Itxaka]

I'm wondering how this makes sense with our splitter chart push. I.E. on this repo we push to our GitHub helm repo but on the readme we mention the opensuse OCI registry.

I guess we should have a different reqdme here pointing to our GitHub resources and then add a different reqdme on the obs build?

Also, would it be possible to generate the readme with some helm plugin that takes those parameters as flags maybe? That would be pretty cool and we could generate it as part of the chart build

Also, docker push jobs doesn't work with forks, only with branches off the main repo so we can ignora that job for now 😀

[fgiudici]

rancher/elemental would seem like the image is on dockerhub ... instead we have:
on github: quay.io/costoolkit/elemental-operator-ci
on OBS: registry.opensuse.org/isv/rancher/elemental/teal52/15.3/rancher/elemental-operator
should we put the full OBS path?

[mjura]

ok, I have provided for now path to quay.io

[fgiudici]

I'm wondering how this makes sense with our splitter chart push. I.E. on this repo we push to our GitHub helm repo but on the readme we mention the opensuse OCI registry.

I guess we should have a different reqdme here pointing to our GitHub resources and then add a different reqdme on the obs build?

Also, would it be possible to generate the readme with some helm plugin that takes those parameters as flags maybe? That would be pretty cool and we could generate it as part of the chart build

Also, docker push jobs doesn't work with forks, only with branches off the main repo so we can ignora that job for now grinning

Or should we mention that the official release is on OBS (all as in the current README) and keep a separate "Dev" instructions detailing the installation from the github?

[Itxaka]

Or should we mention that the official release is on OBS (all as in the current README) and keep a separate "Dev" instructions detailing the installation from the github?

That could also work, dev charts VS official charts, nice!

[fgiudici]

Probably we should add some more context, because we release the chart here on github, while we point to the OBS release in the README here. Anyway, I think this is a good start, we can improve this later.
LGTM, thanks @mjura !