fix warnings in model-registry

[mahdikhashan]

Pull Request Template for Kubeflow Manifests

✏️ Summary of Changes

Describe the changes you have made, including any refactoring or feature additions.

📦 Dependencies

List any dependencies or related PRs (e.g., "Depends on #123").

🐛 Related Issues

Link any issues that are resolved or affected by this PR.

part of #2991

✅ Contributor Checklist

• I have tested these changes with kustomize. See Installation Prerequisites.
• All commits are signed-off to satisfy the DCO check.

---

You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tomcli 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:

• apps/model-registry/upstream/OWNERS

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

[mahdikhashan]

@juliusvonkohout i can not build the kustomization.yaml after using edit fix --vars command, it seems that the auto-fix could not find a parameter,

db:

Error: unable to find field "spec.template.spec.containers.1.args.1" in replacement target

postgres:

Warning: 'Fixed' kustomization now produces the error when running `kustomize build`: unable to find field "spec.template.spec.containers.0.args.2" in replacement target

[juliusvonkohout]

Can you try to do the changes directly here https://github.com/kubeflow/model-registry from where the manifests are synchronized from?

[mahdikhashan]

Can you try to do the changes directly here https://github.com/kubeflow/model-registry from where the manifests are synchronized from?

yes, i'll do so. thank you.

[juliusvonkohout]

can you please rebase both PRs ? so this one and kubeflow/model-registry#813 ?

[mahdikhashan]

can you please rebase both PRs ? so this one and kubeflow/model-registry#813 ?

yes, ill do it tomorrow, hope it's fine with you.

[mahdikhashan]

can you please rebase both PRs ? so this one and kubeflow/model-registry#813 ?

done.

[juliusvonkohout]

can you please rebase both PRs ? so this one and kubeflow/model-registry#813 ?

done.

And fix the tests with a zero diff ;-)

[mahdikhashan]

can you please rebase both PRs ? so this one and kubeflow/model-registry#813 ?

done.

And fix the tests with a zero diff ;-)

sure. i'll do it asap.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[juliusvonkohout]

@vikas-saxena02 do you want to continue here ?

[vikas-saxena02]

@vikas-saxena02 do you want to continue here ?

@juliusvonkohout I jsut took a look, this is an MR on manifest repo itself... dont we first fix upstream and then run the sync script here?

[juliusvonkohout]

@vikas-saxena02 do you want to continue here ?

@juliusvonkohout I jsut took a look, this is an MR on manifest repo itself... dont we first fix upstream and then run the sync script here?

Yes, I think the upstream one is kubeflow/model-registry#813