-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce v1beta1 lifecycle API #2573
Comments
should I create the create common for |
Sorry, @prakrit55 , but this is pretty important since many other tickets depend on this. That's why one of the core maintainers will implement it. Please feel free to take a different ticket :) |
Hey @mowies, I think with a little acquaintance, I could settle it. I have seen the |
Ok if you feel like you're up for it, then go ahead! 😄 |
Goal
The goal of this issue is to move the CRDs from
v1alpha3/v1alpha4
the new API versionv1beta1
.Details
The
v1beta1
version should have the following, which should have the same definition as inv1alpha3/v1alpha4
, those are:KeptnApp
KeptnAppCreationRequest
KeptnAppVersion
KeptnEvaluation
KeptnTask
KeptnTaskDefinition
KeptnWorkload
KeptnWorkloadVersion
The following
v1alpha3
CRDs do not need to be moved tov1beta
:KeptnEvaluationProvider
KeptnWorkloadInstance
Acceptance Criteria
v1beta1
contains the mentioned CRDslifecycle-operator
is installedDoD
v1beta1
version with the mentioned CRDsv1beta1
References
Link to the PoC: #2570
The text was updated successfully, but these errors were encountered: