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

errors after copying over source code and attempting build #101

Open
lknite opened this issue Jul 2, 2024 · 2 comments
Open

errors after copying over source code and attempting build #101

lknite opened this issue Jul 2, 2024 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@lknite
Copy link

lknite commented Jul 2, 2024

switching from dotnet to go over the last couple months, working to implement my first go-based controller

plan was to start from this sample and go from there

copied the code from controller.go and after a 'go mod tidy' am getting the following errors when i compile:

./conNamespace.go:83:22: undefined: workqueue.TypedRateLimitingInterface
./conNamespace.go:108:27: undefined: workqueue.NewTypedMaxOfRateLimiter
./conNamespace.go:109:13: undefined: workqueue.NewTypedItemExponentialFailureRateLimiter
./conNamespace.go:110:14: undefined: workqueue.TypedBucketRateLimiter
./conNamespace.go:120:32: undefined: workqueue.NewTypedRateLimitingQueue

does this code still work? recommend another resource to create my first k8s controller instead of this sample? am i suppose to run an update-codegen.sh script?

@lknite
Copy link
Author

lknite commented Jul 2, 2024

looking into client-go

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants