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 che-operator to the newer operator-sdk. #17828

Closed
AndrienkoAleksandr opened this issue Sep 10, 2020 · 4 comments
Closed

Migrate che-operator to the newer operator-sdk. #17828

AndrienkoAleksandr opened this issue Sep 10, 2020 · 4 comments
Assignees
@tomgeorge
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.
Milestone
7.22

Comments

@AndrienkoAleksandr
Copy link
Contributor

AndrienkoAleksandr commented Sep 10, 2020 •
edited
Loading

Is your enhancement related to a problem? Please describe.

Currently we are using very old one 0.10.0. It is very old version. We have a both: go modules and dep tool, but we want to save and support only go-modules. For development we bounded to the $GOPATH (old operator sdk debugger mode doesn't work with other location).

Describe the solution you'd like

It would be nice to migrate che-operator to the newer operator-sdk. It's not trivial task, because project layout for new operator sdk was very changed, but become mature. And currently we have some CRD limitations, because we still support openshift 3.
@AndrienkoAleksandr AndrienkoAleksandr added kind/enhancement A feature request - must adhere to the feature request template. team/deploy labels Sep 10, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 10, 2020
@tolusha tolusha added area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator and removed team/deploy labels Sep 10, 2020
@tolusha
Copy link
Contributor

tolusha commented Sep 10, 2020

I believe CRD limitation we can bypass by updating it by bash script

@vparfonov vparfonov added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 14, 2020
@tolusha tolusha mentioned this issue Oct 7, 2020
Closed
@tomgeorge
Copy link
Contributor

#18133 also depends on this. I can't import any of the image puller operator types into che-operator without downgrading the image puller operator to a very old version of operator-sdk and kubernetes APIs

@ibuziuk
Copy link
Member

ibuziuk commented Oct 28, 2020

@tomgeorge are you going to start working on this since this looks like a pre-requirement for #18133 ?

@ibuziuk ibuziuk added this to the 7.22 milestone Oct 28, 2020
@tolusha
Copy link
Contributor

tolusha commented Nov 12, 2020

Fixed by eclipse-che/che-operator#515
Migrated to operator-sdk 0.15.2 version

@tolusha tolusha closed this as completed Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomgeorge tomgeorge

Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
7.22
Development

No branches or pull requests
6 participants
@tomgeorge @ibuziuk @vparfonov @tolusha @AndrienkoAleksandr @che-bot