Is it possible to install only controller-gen library?

[LAnastasiia]

Hi! Is it possible to use controller-gen CLI without using kubebuilder?

If yes, how can I install it?
I couldn't find any installation guidelines for controller-gen exclusively. Is there one? (or really any pointer on how to do it would be appreciated)

More context:
Environment does not support kubebuilder integration yet, but does support controller-tools.
From https://book.kubebuilder.io/reference/controller-gen.html#controller-gen-cli it looks like controller-gen covers the need of scaffolding for the project completely. But although I have kubebuilder installed, the controller-gen command can not be found. So I'm looking for a way to install it separately.

Thank you!

[estroz]

You can import things in pkg/ to run generators. controller-gen's main.go is a good (the best?) implementation to reference.

[prashao]

@LAnastasiia To install just the controller-gen binary you can do the following -

1. GOPATH env var should be set
2. export GO111MODULE=on
3. go get sigs.k8s.io/controller-tools/cmd/[email protected]

This will install controller-gen v0.4.1 binary in your GOPATH/bin directory.

[camilamacedo86]

@prashao and @LAnastasiia,

Btw kubebuilder also scaffolds the same install in the Makefile. See; https://github.com/kubernetes-sigs/kubebuilder/blob/master/testdata/project-v3/Makefile#L81-L83

WDYT about we add the install instruction in the README? Would you like to push a PR for that?

Regards:

But although I have kubebuilder installed, the controller-gen command can not be found. So I'm looking for a way to install it separately.

Could you please raise an issue in Kuebuilder repo? Also, please add the Makefile and the version and etc that you are using for we are able to better check that. If it is not working for you we need to see how to fix.

[prashao]

@camilamacedo86
Yeah I'll create a PR to update the README to install standalone controller-gen binary.

[prashao]

@camilamacedo86
Have created PR #537

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.