Skip to content

Conversation

@xrstf
Copy link
Contributor

@xrstf xrstf commented Feb 10, 2025

Summary

Keeping off the discussion regarding how new versions should mature, we decided that for now we just pretend each CRD only has one version in it. This is "more compatible" than requring existing CRDs to define conversion rules.

Related issue(s)

Fixes #20

Release Notes

NONE

@kcp-ci-bot kcp-ci-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has signed the DCO. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 10, 2025
@xrstf xrstf requested a review from embik February 10, 2025 11:49
Copy link
Member

@embik embik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2025
@kcp-ci-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 5d3c090a6e82cb2597a6bcb0748b0c8b92966f29

@kcp-ci-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2025
@kcp-ci-bot kcp-ci-bot merged commit 976d28c into main Feb 10, 2025
10 checks passed
@kcp-ci-bot kcp-ci-bot deleted the drop-versions branch February 10, 2025 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: cannot handle CRDs with multiple versions

3 participants