I am relatively new to Rancher. The way I see the community-catalog is more a playground, than a production safe template list.
My proposal is to create a playground-catalog which should added manually to the catalog list within Rancher.
All community projects should be moved into that playground until they are mature and "ready-to-use-in-production".
My experience in the last 10 days was, that a lot of them are not working, working not as expected, are not maintained or outdated. Also upgrades to newer versions (by using the "upgrade"-button) had break the whole stack irreversible (example mongodb 3.2 -> 3.4), which makes them dangerous to use.
Of course, instead of moving all the projects to another repo (which would break all community-catalog users) one possibility would be to move the mature ones them into a kind of "mature-catalog" repo.
That bullet-proofed repos then should pass a quality (standards) test, before they got really moved into that "mature"-repo.
Hi there,
I am relatively new to Rancher. The way I see the
community-catalogis more a playground, than a production safe template list.My proposal is to create a
playground-catalogwhich should added manually to the catalog list within Rancher.All community projects should be moved into that playground until they are mature and "ready-to-use-in-production".
My experience in the last 10 days was, that a lot of them are not working, working not as expected, are not maintained or outdated. Also upgrades to newer versions (by using the "upgrade"-button) had break the whole stack irreversible (example mongodb 3.2 -> 3.4), which makes them dangerous to use.
Of course, instead of moving all the projects to another repo (which would break all community-catalog users) one possibility would be to move the mature ones them into a kind of "mature-catalog" repo.
That bullet-proofed repos then should pass a quality (standards) test, before they got really moved into that "mature"-repo.
What are your thoughts?