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

incorrect usage of k8s.io/kubernetes #1537

Closed
carnott-snap opened this issue Nov 9, 2019 · 3 comments
Closed

incorrect usage of k8s.io/kubernetes #1537

carnott-snap opened this issue Nov 9, 2019 · 3 comments
Assignees
Labels
area/build-and-release kind/bug priority/backlog Not staffed at the moment. Help wanted.

Comments

@carnott-snap
Copy link

What happened?
When importing eksctl as a library, I pull in k8s.io/kubernetes as a transitive dependency.

I would like to use the k8s.io/kubernetes/pkg/cloudprovider/providers/aws package version that is compatible with the other kubernetes-1.12.6 libraries that I am importing. I am aware that we should not import k8s.io/kubernetes directly, per kubernetes/kubernetes#81878. I looked in kubernetes/cloud-providers-aws, however I do not see any kubernetes-1.12.6 tag and the code was removed at kubernetes/cloud-provider-aws@b377713.

What you expected to happen?
Customers should not import k8s.io/kubernetes directly, see kubernetes/kubernetes#81878, and instead using component modules: k8s.io/cloud-provider and k8s.io/cloud-provider-aws.

Anything else we need to know?
I would have submitted this as a PR, since the k8s.io/cloud-provider fix is just a find -exec sed, unfortunately I am unclear what the best candidate for replacing k8s.io/kubernetes/pkg/cloudprovider/providers/aws is. kubernetes/cloud-providers-aws does not have any tags, let alone kubernetes-1.12.6, and the related logic was removed: kubernetes/cloud-provider-aws@b377713. As such, I have created an upstream ticket to track the need: kubernetes/kubernetes#85022.

@michaelbeaumont
Copy link
Contributor

This specific usage of k8s.io/kubernetes is gone but another remains since https://github.com/weaveworks/eksctl/pull/2227/files

michaelbeaumont added a commit to michaelbeaumont/eksctl that referenced this issue Jun 10, 2020
According to
golang/go#32776 (comment), it's
not supposed to be used as a dependency.

Additionally, I think this code might end up being removed if we agree
with golang/go#32776 (comment).

Closes eksctl-io#1537
michaelbeaumont added a commit to michaelbeaumont/eksctl that referenced this issue Jun 10, 2020
According to
golang/go#32776 (comment), it's
not supposed to be used as a dependency.

Additionally, I think this code might end up being removed if we agree
with eksctl-io#2197 (comment).

Closes eksctl-io#1537
michaelbeaumont added a commit to michaelbeaumont/eksctl that referenced this issue Jun 10, 2020
According to
golang/go#32776 (comment), it's
not supposed to be used as a dependency.

Additionally, I think this code might end up being removed if we agree
with eksctl-io#2197 (comment).

Closes eksctl-io#1537
@martina-if martina-if added the priority/backlog Not staffed at the moment. Help wanted. label Sep 15, 2020
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Jan 18, 2021
@michaelbeaumont
Copy link
Contributor

Duplicate of #813

@michaelbeaumont michaelbeaumont marked this as a duplicate of #813 Jan 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-and-release kind/bug priority/backlog Not staffed at the moment. Help wanted.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants