-
Notifications
You must be signed in to change notification settings - Fork 14
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
Providers/Templates compatibility based on contracts instead of versions #496
Comments
zerospiel
added a commit
to zerospiel/hmc
that referenced
this issue
Oct 18, 2024
* removed version/constraints from compatibility attributes * compatibility is now based on CAPI contracts versions * unified providers structure * corresponding adjustments Closes Mirantis#496
zerospiel
added a commit
to zerospiel/hmc
that referenced
this issue
Oct 18, 2024
* removed version/constraints from compatibility attributes * compatibility is now based on CAPI contracts versions * unified providers structure * corresponding adjustments Closes Mirantis#496
zerospiel
added a commit
to zerospiel/hmc
that referenced
this issue
Oct 18, 2024
* removed version/constraints from compatibility attributes * compatibility is now based on CAPI contracts versions * unified providers structure * corresponding adjustments Closes Mirantis#496
zerospiel
added a commit
to zerospiel/hmc
that referenced
this issue
Oct 18, 2024
* removed version/constraints from compatibility attributes * compatibility is now based on CAPI contracts versions * unified providers structure * corresponding adjustments Closes Mirantis#496
zerospiel
added a commit
to zerospiel/hmc
that referenced
this issue
Oct 18, 2024
* removed version/constraints from compatibility attributes * compatibility is now based on CAPI contracts versions * unified providers structure * corresponding adjustments Closes Mirantis#496
zerospiel
added a commit
to zerospiel/hmc
that referenced
this issue
Oct 18, 2024
* removed version/constraints from compatibility attributes * compatibility is now based on CAPI contracts versions * unified providers structure * corresponding adjustments Closes Mirantis#496
zerospiel
added a commit
to zerospiel/hmc
that referenced
this issue
Oct 21, 2024
* removed version/constraints from compatibility attributes * compatibility is now based on CAPI contracts versions * unified providers structure * corresponding adjustments Closes Mirantis#496
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://cluster-api.sigs.k8s.io/developer/providers/contracts
Examples:
for core capi current supported contracts are v1alpha3,v1alpha4,v1beta1
for aws:
For azure and vsphere:
For core capi exposed contracts: v1alpha3,v1alpha4,v1beta1
For providers - expected capi core contracts, supported provider contracts
For clustertemplates set required provider contracts only (we assume that the core contract will be aligned) and validate against the current state of the Management object status.
The text was updated successfully, but these errors were encountered: