tldr - powered by Generative AI

• CRDs are used to extend Kubernetes and as projects grow, the definitions of the resource start to evolve and may completely change, requiring versioning of CRDs
• Versioning of CRDs can be tough as end users need to be provided with seamless upgrades, zero downtime and backwards compatibility
• There are two views of CRD versioning: server version and stored version
• There are two conversion strategies: last mile change and full conversion
• The conversion package simplifies conversion functions between API versions
• The storage version migrator component bumps up existing objects to the new desired storage version
• Lossless conversion is followed where users can roll back to the older version
• Annotations of the field of the CR are used to store functions which lose data between versions