-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Unable to use CRDs imported as modules #3770
Comments
Hi @nixx thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
Hi @nixx the Ingress Controller is not really designed to be imported as a module. Can you share more info about your workflow and how you use it as a module? I think it's the first time we hear about this use case 🙂 |
Hi @nixx, |
reopening as merging #4152 is causing local build issue as described in #4324 |
Work on this item can be resumed when we get more information from @nixx, and possible target V4 (version 4.0.0) of the |
Describe the bug
When automating the configuration for NGINX Ingress Controller, we need access to the CRDs. Importing them as a golang module, is preferrable.
To Reproduce
Steps to reproduce the behavior:
Running " go get -u github.com/nginxinc/kubernetes-ingress" will fail with " require github.com/nginxinc/kubernetes-ingress: version "v3.1.0" invalid: should be v0 or v1, not v3"
This is fixable with adding /v3 in the module name in go.mod.
Expected behavior
Expecting to be able to import the module.
I do get around it with psedo-versions (go get -u github.com/nginxinc/[email protected])
Your environment
v3.1.0
Kubernetes: N/A
The text was updated successfully, but these errors were encountered: