Open petersutter opened 6 years ago
Please keep in mind, that there is also a cache for available updates / upgrades for a specific k8 version / cloudprofile in the frontend. We need to adopt this logic to watch cloudprofile changes, too.
will be done as part of the refactoring
Currently the frontend only fetches the cloudprofiles once "per session". When the cloud profiles get updated it can happen that the browser still has the "old" cloudprofile values and the creation of a new cluster could fail. E.g. if the selected kubernetes version does not match one of the allowed kubernetes versions specified in the corresponding cloud profile.