-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to upgrade providers when using custom fetchconfig #570
Comments
/triage accepted |
As discussed in the CAPI Operator office hours, we might want to reach out to CAPI Maintainers and discuss the possible solution. |
/assign @w21froster |
@furkatgofurov7: GitHub didn't allow me to assign the following users: w21froster. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Probably, I understand the nature of this problem.
It's necessary to add a validation at the manifest parsing phase, for the following rule: As alternative way, we could get a provider name from the manifest Will take care about this issue. P.S. For example, if it validation is not passed, I can install any type of provider, i.e. helm addon as any type of the operator custom resource, as Infrastructure or Core, that's wrong behavior. |
/assign |
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: