search

giantswarm / roadmap

Giant Swarm Product Roadmap
https://github.com/orgs/giantswarm/projects/273
Apache License 2.0
3 stars 0 forks source link

Make apps in MCF configurable per-MC, instead of per-provider, so that we can have more granular upgrade scenarios #1904

Open gianfranco-l opened 1 year ago

gianfranco-l commented 1 year ago

Make apps in MCF configurable per-MC, instead of per-provider, so that we can have more granular upgrade scenarios

related: Pull based app collections

weatherhog commented 1 month ago

@uvegla @ljakimczuk could one of you check if this issue is still valid?

ljakimczuk commented 1 month ago

@weatherhog Well, I believe this may still be valid as a general improvement, but also I am not sure doing this is easily possible - we can re-evaluate it. I think it is about collection being the place where configuration for apps is generate at, and if something gets there, it gets to all clusters using given collection. If we wanted to deploy a new version of an app only to selected cluster(s), we need to apply patches inside fleet repository / repositories, where we tell clusters to use collection, or suspend Flux in these target cluster(s) and then change versions, what we usually do for testing, but none of these probably feel like a structured approach to the problem. But I have gut feeling we cannot make it more granular and structure without incurring some costs, like code duplication or sacrificing maintainability, but who knows.

uvegla commented 1 month ago

Potentially related to: https://github.com/giantswarm/giantswarm/issues/31342? 🤔