Unable to upgrade providers when using custom fetchconfig #570
Labels
kind/bug
Categorizes issue or PR as related to a bug.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What steps did you take and what happened:
When trying to perform an upgrade of already deployed providers, configured for airgapped environment (custom config map), I have the following error in each provider's controller logs:
Here, controller AddonProvider seems to check configuration of an InfrastructureProvider, but I have same error for BootstrapProvider controller for example, and InfrastructureProvider is complaining about BootstrapProvider:
If i delete current provider version and apply new one, this provider is deployed without error, so the fetchConfig seems to be ok.
What did you expect to happen:
Upgrade of providers should happens no matter what kind of configuration is used (custom fetchconfig or "github manifest").
Anything else you would like to add:
Here is a full log about a controller reconciliation showing that it detects that version has changed but fails to perform upgrade:
From my understanding issue come from the fact that known providers list remains the default one. The current controller is only aware of it's own provider custom configuration (see here) where it should have all providers custom infos to be able to check them here in this loop.
Environment:
kubectl version
): v1.28.7/etc/os-release
): Ubuntu 22.04.4 LTS/kind bug
The text was updated successfully, but these errors were encountered: