Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Use case. Why is this important?
Modules in FE/EE/CE must have the same digest for container images. If the are built with with different images - it will raise a problem during the runtime
Proposed Solution
Have to make some script, which will take all modules from the FE registry:
crane ls registry.deckhouse.io/deckhouse/fe/modules
For each module, scan the release images:
crane ls registry.deckhouse.io/deckhouse/fe/modules/virtualization | grep "^v"
For each release get the config:
crane config registry.deckhouse.io/deckhouse/fe/modules/virtualization:$release | jq . > $release.fe.json
also get all releases for EE and CE
crane config registry.deckhouse.io/deckhouse/ee/modules/virtualization:$release | jq . > $release.ee.json
...
Compare them:
diff $release.fe.json $release.ee.json
diff $release.fe.json $release.ce.json
these files must be equal. If they are not, we have to report the module with problems
Additional Information
We need a script to run it manually.
Also can to a scheduler job (once per week for example) and report for wrong-built modules