Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Migrate to the new Kubebuilder based Operator SDK framework #969

Closed
zroubalik opened this issue Aug 6, 2020 · 2 comments
Closed

Migrate to the new Kubebuilder based Operator SDK framework #969

zroubalik opened this issue Aug 6, 2020 · 2 comments
Assignees
@zroubalik
Labels
feature-request All issues for new features that have not been committed to
Milestone
v2.0

Comments

@zroubalik
Copy link
Member

From v0.19 Operator SDK project was merged with Kubebuilder, this results in a new project layout (ie. KEDA code layout at build stuff).

We should migrate to the new project structure for v2.

https://sdk.operatorframework.io/docs/golang/quickstart/
@zroubalik zroubalik added the feature-request All issues for new features that have not been committed to label Aug 6, 2020
@zroubalik zroubalik added this to the v2.0 milestone Aug 6, 2020
@zroubalik zroubalik self-assigned this Aug 6, 2020
@tomkerkhove
Copy link
Member

Notes from standup yesterday:

  • We are using Operator SDK which is being merged with Kubebuilder, we should check if we can migrate
  • Has no functionality changes but just reshuffling of the code
  • No objections, will be done for 2.0 stable release

@zroubalik zroubalik mentioned this issue Aug 18, 2020
Merged
2 tasks
@zroubalik
Copy link
Member Author

Fixed by #1007

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zroubalik zroubalik

Labels
feature-request All issues for new features that have not been committed to
Projects
None yet
Milestone
v2.0
Development

No branches or pull requests
2 participants
@zroubalik @tomkerkhove