Keep cloud-provider-openstack app up to date

[cornelius-keller]

We need to keep cloud provider app openstack up to date

[cornelius-keller]

@giantswarm/team-rocket do we still need this issue?

[erkanerol]

I think yes. We don't have any automation which updates our dependencies yet.

[bavarianbidi]

as occm doesn't change that often and releases are mostly done to support upcoming kubernetes versions i would propose the following for now:

1. track cloud-provider-openstack releases (if you use an rss-reader: https://github.com/kubernetes/cloud-provider-openstack/releases.atom)
2. and create a version-bump-PR

As this is a general issue (with external manifests/containers) we could think about implementing/extending something like a dependabot which does most of this stuff automatically and then trigger some tests (create cluster, apply cloud-controller-manager, do stuff via k8s api which depends on cloud-controller-manager stuff - e.g. create a pv, create a service with type Loadbalancer, ...). But for this we should create a design-proposal (detailed RFC) - WDYT?

[cornelius-keller]

I think making it more generic and thinking also about how to keep all the other stuff up to date would be great. Team honeybadger has already some plans for this, I think we should hook in there. Please have a look at #391 (comment) and the corresponding epic https://github.com/giantswarm/giantswarm/issues/20641.

[kubasobon]

👋 Hi, I'd be grateful if you could take a glance at giantswarm/rfc#33. That's our proposed solution to automate App and CAPI cluster upgrades.

[kopiczko]

It isn't that simple because it's a part of default-apps-openstack