-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Got errors on kubebuilder v3 quick start #3016
Comments
|
May I know what changes you did to the leader election? For this - Enable the leader-election |
On generated
|
Using
This error is a bit different. I'm not sure why it would be getting a permission denied when attempting to load the kubeconfig. It seems possible it could be related to If you update the config/rbac/service_account.yaml file and add this to the end of it: automountServiceAccountToken: true does running |
After running through the tutorial locally and using
I even attempted it after forcing the
I did not need to do:
|
That should not be necessary. Service accounts still mount tokens by default in 1.24, they just do so using ephemerally generated tokens, not tokens stored in Secret API objects |
My cluster K8s version is:
Kubebuilder version is:
With these context, will replicate the error. @everettraven |
Hi @liggitt, The following steps are not accurate.
Could you please perform the suggested steps to check if the error is still faced? |
@camilamacedo86 I modified this first, and then |
Hi @astraw99, I see. If you enable the leader election you are facing the problem a) Is the issue faced when/if you update the config/manager.yaml to pass the flag == true and deploy the project on the cluster as well? OR the namespace is only required if/when you run it outside of the cluster for developing/test purposes with make run? PS.: Note that in the quick start we do not have any step saying for someone to enable the leader election. Therefore, the title/description here does not seem accurate. It is more like so far "default scaffold does not work if/when we enable leader election and we use make run to test the project outside of the cluster" |
Yes, it is the |
HI @astraw99, Is the same error faced using make deploy IMG or not? |
/label triage/accepted |
Hi @astraw99,
The default scaffold does have not SA. So, how can that can be faced by default? However, this issue was used to just add the manifest target to the make build target (#3020). Let's discuss the other points in the #3028 |
What broke? What's expected?
Using the latest kubebuilder cli, quick start a new project based on the official document, got these errors:
make run
, got error:make deploy IMG=xxx/xxx:tag
, the controller-pod got error:Important: Run "make" to regenerate code after modifying this file
, butmake
did not generate latest CRD fields.Reproducing this issue
Just quick start a new project based on the official document, then will reproduce this issue.
KubeBuilder (CLI) Version
Version: main.version{KubeBuilderVersion:"3.7.0", KubernetesVendor:"1.24.1", GitCommit:"3bfc84ec8767fa760d1771ce7a0cb05a9a8f6286", BuildDate:"2022-09-20T17:21:57Z", GoOs:"darwin", GoArch:"amd64"}
PROJECT version
No response
Plugin versions
No response
Other versions
No response
Extra Labels
No response
The text was updated successfully, but these errors were encountered: