Summary:

• Understand the mechanisms involved when bumping a CRD version from one version to another, e.g. v1beta1 to v1beta2.

Goal:

• Determine how apiVersion bumps for CRDs within the RHOSO product could be addressed and managed.
• Investigate the various options and identify which ones are good candidates for further evaluation. Identify if there are any items that are poor candidates for further investigation.
• Review the usage of conversion webhooks and their place within the openstack-operator and the RHOSO product as a whole. Determine if these are a good candidate for further investigation.
• Identify how version bumps could impact the OpenStackControlPlane CRD.

TimeBox:

• 2 weeks.

Deliverables/Outcomes:

• Identify and document the most appropriate avenues to pursue the ability to manage apiVersion changes within the RHOSO product.
• Note which interfaces have the potential to be used and which ones would cause us problems.
• Identify risks and interfaces that would be affected by version bumps, particularly when moving between minor releases and major releases.
• Open an Initiative after the information is identified, and build out the template to cover the goals and targets required to support CRD version bumps within the RHOSO product. Identify when these version bumps could happen, and when it would not be appropriate for the version bumps to be implemented as it would garner too much risk to the product.