update API Provider to v1beta1#399
update API Provider to v1beta1#399anish-mudaraddi wants to merge 9 commits intoazimuth-cloud:mainfrom anish-mudaraddi:update-api-provider
Conversation
update api provider to use v1beta1 since its provided in newest cluster api provider version 0.10.*
made further changes for openstackmachinetemplate and openstackcluster to to be compatible with v1beta1 api provider version
|
I've made the necessary changes - and I've tested making a cluster with the changes and its working for me! |
|
@anish-mudaraddi the etcd test is failing, looks like we need this change as well. |
mkjpryor
left a comment
There was a problem hiding this comment.
This PR is a good start, but while we are moving to a new API version I'd like to take the opportunity to adopt some of the new functionality. Some examples would be:
- Moving the external network specification to a proper filter but still respecting the old-style ID for backwards compatibility
- Supporting multiple subnets but still respecting the old-style single subnet configuration for backwards compatibility
- ...
I understand that you want this quickly to correct your issues with Argo CD, but it seems like a good opportunity to also do these things.
|
It is also important that all of these changes are implemented in a backwards-compatible way. This means that where fields have changed their name, e.g. |
|
@mkjpryor no problem - I'll try to implement the functionality you requested! |
v1beta1 changes the names of the following for the rootVolume field: - diskSize to sizeGiB - volumeType to type it also changes the way availabilityZone name is provided This commit ensures that the changes are backwards compatible and deprecates the changes in values.yaml
allow users to specify additional security groups using managedSecurityGroups. Allow backwards compatibility with previous way which set it as a boolean
allow users to specify if they want to disable external networking for the cluster allow users to utilise filter methods available in v1beta1 for specifying external network - ensured backwards compatibility with externalNetworkiD
v1beta1 allows specifying 2 subnets for dual stack configuration. It also adds the managedSubnets field. This commit adds these and also maintains backwards compatibility
allows specifying serverGroupFilter instead of serverGroupId for machine templates but maintaining backwards compatibility
|
I've implemented the following changes:
Bits I left out
|
|
@anish-mudaraddi Can you rebase this onto |
|
I'm finding this PR very hard to review. Thinking on it some more, I think I would prefer to split this change into two PRs:
|
|
I think #423 is the minimal set of changes needed to move to |
| # The size of the disk to use in gibibytes (GiB) | ||
| # If not given, the ephemeral root disk from the flavor is used | ||
| diskSize: | ||
| sizeGiB: |
There was a problem hiding this comment.
Hmm, I fear some of these are going to break a lot of users' templates without some help to migrate between the old and new values here. 🤔 @mkjpryor any ideas on how to help with that?
|
Superseded by #423 for now |
An attempt to fix issue #398
update api provider to use v1beta1 since its provided in newest cluster api provider version 0.10.*