We are open to better name suggestions as well !!

can i try to solve this

@rovertrack just comment here /assign and the issue will be assigned to you (so that 2 people do not work on the same task)

if you need any help, just ping here or in the PR

/assign

where the kubebuilderVersion has to be in the projectfile

currently, a sample PROJECT file looks like this

# Code generated by tool. DO NOT EDIT.
# This file is used to track the info used to scaffold your project
# and allow the plugins properly work.
# More info: https://book.kubebuilder.io/reference/project-config.html
domain: openshift.io
layout:
- go.kubebuilder.io/v4
projectName: oadp-nac
repo: github.com/migtools/oadp-non-admin
resources:
- api:
    crdVersion: v1
    namespaced: true
  controller: true
  domain: openshift.io
  group: oadp
  kind: NonAdminBackup
  path: github.com/migtools/oadp-non-admin/api/v1alpha1
  version: v1alpha1
version: "3"

I think it makes sense to be a high level information, like version

It would look like this then

# Code generated by tool. DO NOT EDIT.
# This file is used to track the info used to scaffold your project
# and allow the plugins properly work.
# More info: https://book.kubebuilder.io/reference/project-config.html
domain: openshift.io
layout:
- go.kubebuilder.io/v4
projectName: oadp-nac
repo: github.com/migtools/oadp-non-admin
resources:
- api:
    crdVersion: v1
    namespaced: true
  controller: true
  domain: openshift.io
  group: oadp
  kind: NonAdminBackup
  path: github.com/migtools/oadp-non-admin/api/v1alpha1
  version: v1alpha1
version: "3"
kubebuilderVersion: "3.14.2"

👍

/assign

@camilamacedo86 @mateusoliveira43 Hi, I was just browsing through issues with good first issue and came across this issue and (#4297) with the hopes of contributing 😄 but I see that we already have 2 assignees.

May I suggest we have the k8s-ci-robot limit to 1 asignee max per issue? and reject future /assign commands if there is an assignee already? This way, we know who is working on it and prevent other folks from just snatch it..

Hi @jameskim0987,

It’s possible they are working together—more than one person can collaborate on a task.
That it is why I think is not a good idea.

That said, it’s also common for someone to assign themselves to an issue but later be unable to follow through due to unforeseen circumstances.

To address this, I usually monitor tasks that have been assigned but remain inactive for some time. Afterward, I reach out to the assignees to check in.

I also encourage contributors to be proactive by:

• Reaching out to the assignee directly.
• Sending a quick ping in Slack to check if they’re stuck or need assistance.
• Offering to help if the other person cannot move forward.
• This way, we can keep things moving and avoid blockers.

@camilamacedo86 Got it. Thank you for providing clarity on this matter.

@sureshkrishnan-v @rovertrack

Are you both working on this one?
Did you need any help?
If you are not working, please unsigned so that others can help.

/assign

/unassign

/assign

@camilamacedo86 I suspect this change would go with adding kubebuilderVersion: "4.x.x" in every PROJECT config file and updating the respective docs.

Along with that you need to test it out locally as mentioned here
https://github.com/kubernetes-sigs/kubebuilder/pull/4302/files#diff-839fbabd902ec0394e11ba9817c2ae1fb54998acd4d9dd46cebb62217ea96a7cR193

@camilamacedo86 I suspect this change would go with adding kubebuilderVersion: "4.x.x" in every PROJECT config file and updating the respective docs.

Yes, that is the final result that we want.
When we call kubebuilder init and we generate the scaffold we would have the version used (kubebuilder version) of the CLI in the PROJECT file.

Along with that you need to test it out locally as mentioned here
https://github.com/kubernetes-sigs/kubebuilder/pull/4302/files#diff-839fbabd902ec0394e11ba9817c2ae1fb54998acd4d9dd46cebb62217ea96a7cR193

This change/RFE will be helpful for the WIP proposal because we will need to know what version was used to do the original scaffold, but this task itself has no dependency within it.

@akagami-harsh Are you working on this one? Need any help?

/assign

@camilamacedo86 I'm curious about how this new field will be handled in existing projects. Will it only be added during initial scaffolding, or should we also check for and update it when making changes to an existing project? I guess it wouldn't be safe to assume that the version used to update the project is the same that was used for scaffolding, right? 🤔

But I still think it could be useful to track the CLI version even during updates because it can help with troubleshooting and compatibility issues. If someone updates their project with a newer version of Kubebuilder, knowing that version along with the original version could be helpful. But I guess that's an issue for another time. 😉

@vitorfloriano I was thinking about this

Should we add check, during execution of any command that would touch PROJECT file, check if version in the file is the same as the one of the CLI?

Example

I created project with kubebuilder version 3.14.0 (which does not contain field) and now I adding a controller with version 4.6.0.

We could error operation saying user must use same version used to scaffold the project to scaffold new code, pointing to documentation on how to update code.

We could also add in error message if the user wants to override this check, just manually add/update kubebuilder version in PROJECT file.

This can be done in a separate issue as well, if agreed. cc @camilamacedo86