Replace gRPC code generation tool from Znly/protoc to Buf

[shivas1516]

This commit updates the codebase to utilize Buf for generating gRPC code instead of Zync.

What this PR does / why we need it:

This PR replaces the outdated code generation tool 'znly/protoc' with Buf for generating gRPC code. The change is necessary due to the lack of maintenance and updates for 'znly/protoc', ensuring compatibility, security, and access to new features with Buf.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2141

Checklist:

• Docs included if any changes are user facing

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: shivas1516
Once this PR has been reviewed and has the lgtm label, please assign andreyvelich for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tenzen-y]

@shivas1516 Thank you for this contribution!
First of all, could you sign cla and DCO?

[shivas1516]

Of course! I'm glad you found my contribution valuable. Before proceeding, may I ask if you could kindly provide more context or details regarding the CLA and DCO you mentioned? That way, I can better assist you with the signing process.

[tenzen-y]

Of course! I'm glad you found my contribution valuable. Before proceeding, may I ask if you could kindly provide more context or details regarding the CLA and DCO you mentioned? That way, I can better assist you with the signing process.

Sure.

CLA singing step: https://github.com/kubeflow/katib/pull/2277/checks?check_run_id=22474756817
DCO signing step: https://github.com/kubeflow/katib/pull/2277/checks?check_run_id=22474756788

[shivas1516]

Of course! I'm glad you found my contribution valuable. Before proceeding, may I ask if you could kindly provide more context or details regarding the CLA and DCO you mentioned? That way, I can better assist you with the signing process.

Sure.

CLA singing step: https://github.com/kubeflow/katib/pull/2277/checks?check_run_id=22474756817 DCO signing step: https://github.com/kubeflow/katib/pull/2277/checks?check_run_id=22474756788

I really appreciate your time and patience. Just to let you know, I've signed both the CLA and the DCO. Thanks again for your help! Looking forward for any suggestions you might have for this PR

[tenzen-y]

@kubeflow/wg-automl-leads
Could you approve CI? Checking the result of CI would be helpful before we review this.

[tenzen-y]

@shivas1516 Could you address CI errors?

[shivas1516]

@shivas1516 Could you address CI errors?

Ofcourse, Let me rework on this CI errors. If any Suggestions regarding this CI Errors please let me know, That will help me to move forward in a correct way faster.

[andreyvelich]

Thank you for your contribution @shivas1516 🎉
Did we investigate what tools other Kubeflow components are using to generate protobufs ?
For example, Kubeflow Pipelines ?

[shivas1516]

Thank you for your contribution @shivas1516 🎉 Did we investigate what tools other Kubeflow components are using to generate protobufs ? For example, Kubeflow Pipelines ?

@andreyvelich Unfortunately, I'm just getting back to you now. I've been tied up addressing the CI errors in this PR. However, I'm having difficulty grasping your thoughts clearly. Could you please provide some detailed explanation for better clarity?

[andreyvelich]

Thank you for your contribution @shivas1516 🎉 Did we investigate what tools other Kubeflow components are using to generate protobufs ? For example, Kubeflow Pipelines ?

@andreyvelich Unfortunately, I'm just getting back to you now. I've been tied up addressing the CI errors in this PR. However, I'm having difficulty grasping your thoughts clearly. Could you please provide some detailed explanation for better clarity?

@shivas1516 Currently, if we make any changes in api.proto, we can run make generate to re-generate files. Since you are going to remove pkg/apis/manager/health/build.sh file, how we can re-generate gRPC files ?

[shivas1516]

Thank you for your contribution @shivas1516 🎉 Did we investigate what tools other Kubeflow components are using to generate protobufs ? For example, Kubeflow Pipelines ?

@andreyvelich Unfortunately, I'm just getting back to you now. I've been tied up addressing the CI errors in this PR. However, I'm having difficulty grasping your thoughts clearly. Could you please provide some detailed explanation for better clarity?

@shivas1516 Currently, if we make any changes in api.proto, we can run make generate to re-generate files. Since you are going to remove pkg/apis/manager/health/build.sh file, how we can re-generate gRPC files ?

@andreyvelich When migrating to Buf, instead of using make generate, we must utilize the buf generate command to regenerate code changes in .proto files. This command relies on configurations specified in buf.gen.yaml, where we can define language preferences for generating code, remote plugins to use, and versions for our convenience.

Hope I'm clear to you, If any suggestions or need clarity regarding this. Please let me know.

[tenzen-y]

When migrating to Buf, instead of using make generate, we must utilize the buf generate command to regenerate code changes in .proto files. This command relies on configurations specified in buf.gen.yaml, where we can define language preferences for generating code, remote plugins to use, and versions for our convenience.

Hope I'm clear to you, If any suggestions or need clarity regarding this. Please let me know.

@shivas1516 Any reasons that you closed this PR?

[shivas1516]

When migrating to Buf, instead of using make generate, we must utilize the buf generate command to regenerate code changes in .proto files. This command relies on configurations specified in buf.gen.yaml, where we can define language preferences for generating code, remote plugins to use, and versions for our convenience.

Hope I'm clear to you, If any suggestions or need clarity regarding this. Please let me know.

@shivas1516 Any reasons that you closed this PR?

Thank you for your inquiry regarding the closure of the PR.

Unfortunately, the PR was closed due to an error that occurred in the my forked Katib repository GitHub codespace. Regrettably, I had to delete the forked repository master as a result. However, I am currently reworking on this issue, and I am confident that it will be even better this time around. I have reached out to the Buf community and received valuable suggestions from them, which I believe will contribute to the improvement of the project.

[tenzen-y]

When migrating to Buf, instead of using make generate, we must utilize the buf generate command to regenerate code changes in .proto files. This command relies on configurations specified in buf.gen.yaml, where we can define language preferences for generating code, remote plugins to use, and versions for our convenience.
Hope I'm clear to you, If any suggestions or need clarity regarding this. Please let me know.

@shivas1516 Any reasons that you closed this PR?

Thank you for your inquiry regarding the closure of the PR.

Unfortunately, the PR was closed due to an error that occurred in the my forked Katib repository GitHub codespace. Regrettably, I had to delete the forked repository master as a result. However, I am currently reworking on this issue, and I am confident that it will be even better this time around. I have reached out to the Buf community and received valuable suggestions from them, which I believe will contribute to the improvement of the project.

Thank you for your effort. I just wanted to confirm if you're still in here.