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.

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

Upgrade to operator-sdk v1.3.0 #266

Closed
ytsarev opened this issue Jan 25, 2021 · 0 comments · Fixed by #276
Closed

Upgrade to operator-sdk v1.3.0 #266

ytsarev opened this issue Jan 25, 2021 · 0 comments · Fixed by #276
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@ytsarev
Copy link
Member

ytsarev commented Jan 25, 2021

Upgrade to https://github.com/operator-framework/operator-sdk/releases/tag/v1.3.0

It should probably also solve all current dependabot non-compatible upgrade suggestions

@ytsarev ytsarev added the enhancement New feature or request label Jan 25, 2021
@ytsarev ytsarev added this to the 0.8 milestone Jan 25, 2021
@kuritka kuritka self-assigned this Feb 2, 2021
kuritka added a commit that referenced this issue Feb 2, 2021
Closes #266

I gradually bumped from v1.0.0 (default) to 1.3.0
(1.1.0 didn't have impact on us)
https://sdk.operatorframework.io/docs/upgrading-sdk-version/
Operator SDK uses v0.20.0. **Dependabot failed** because it bumps always one of the three packages that needs to be bumped
(viz my comment)

missing zapr v0.4.0 caused failing tests (missing interface in default zapr v0.1.0 caused runtime errors of logr v0.4.0)
Both zapr and logr must be bumped together
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants