-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
k8sutil moved to internal package #3792
Comments
@Kaitou786 The helper libraries that did exist and are still relevant have been moved to Your project should no longer depend directly on Can you provide more details about the issue you're running into?
|
Ah okay,
2: Running
|
Can you try removing |
Thanks, it replaced it with an earlier version of operator-sdk, |
Also, have you read the 1.0 migration guide? Among some other great benefits to using the new project layout, you may be able to drastically reduce the content of your go.mod file by re-scaffolding your project with |
@joelanford, actually I was following that guide only, and re-scaffolded by |
Ok cool! Yeah, that must mean that one of your project's dependencies still pulls in an older version of Sounds like you're good to go now though, so I'll close this one. If you encounter anything else while migrating, definitely open more issues! |
@joelanford just out of curiosity does the |
It is, things are restructured a bit. Generated packagemanifests and bundles will end up in the project root directory. There are some base files that are used to generate packagemanifests and bundles in |
For me it didn't work. github.com/operator-framework/operator-sdk/pkg/k8sutil: module github.com/operator-framework/operator-sdk@latest found (v1.11.0), but does not contain package github.com/operator-framework/operator-sdk/pkg/k8sutil @joelanford can you help me here. |
Bug Report
What did you do?
Upgrade operator-sdk from 0.18.2 -> 1.0.0
What did you expect to see?
Hi, we were in the process of upgrading our golang operator from 0.18.x to 1.0.0, and noticed k8sutil has been moved to an internal package, we removed its dependency from our codebase but, some of our other dependency like operator-marketplace still imports it causing our upgrade to halt. So I just wanted to ask is there any specific reason for why it is moved to an internal package now? I think it was used by many other projects as well
What did you see instead? Under which circumstances?
Environment
Operator type:
The text was updated successfully, but these errors were encountered: