Skip to content

Conversation

@jyejare
Copy link
Contributor

@jyejare jyejare commented Nov 27, 2025

What this PR does / why we need it:

This PR now switches the feast operator to API version from v1alpha1 to v1 as a production ready operator with no more alpha tag.

Which issue(s) this PR fixes:

Closes Jira https://issues.redhat.com/browse/RHOAIENG-39324

Misc

@jyejare jyejare requested a review from a team as a code owner November 27, 2025 14:17
@jyejare jyejare changed the title Production ready feast operator with v1 apiversion feat: Production ready feast operator with v1 apiversion Nov 27, 2025
@jyejare jyejare force-pushed the noalpha branch 11 times, most recently from 1498b3d to dbae106 Compare December 10, 2025 15:24
Signed-off-by: jyejare <jyejare@redhat.com>
@@ -0,0 +1,45 @@
# This patch adds v1alpha1 as a deprecated version to support migration from previous versions
Copy link
Member

Choose a reason for hiding this comment

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

@jyejare rather than using rename + patch approach, I think we should use kubebuilder standard approach for API version upgrades, where we keep both v1 and v1aplha1 like:

api/
├── v1/
│   ├── featurestore_types.go      (+kubebuilder:storageversion)
│   ├── groupversion_info.go
│   └── zz_generated.deepcopy.go
└── v1alpha1/
    ├── featurestore_types.go      (+kubebuilder:deprecatedversion)
    ├── groupversion_info.go
    └── zz_generated.deepcopy.go

and CRD will look like:

versions:
- name: v1
  storage: true           # Primary storage version
  # Full schema...
  
- name: v1alpha1
  storage: false          # Deprecated, not stored
  deprecated: true
  deprecationWarning: "feast.dev/v1alpha1 FeatureStore is deprecated, use feast.dev/v1 instead"
  # Full schema (for validation)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, I tried that with latest update but I think there is something wrong with our tests. I am closing this PR as I have messed up the changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Opened #5771

@jyejare jyejare closed this Dec 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants