Skip to content
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

Fix bug: Remove redundant helm chart affinity on predictor CRD #3481

Merged
merged 1 commit into from
Mar 24, 2024

Conversation

trojaond
Copy link
Contributor

@trojaond trojaond commented Feb 27, 2024

labels:

  • app.kubernetes.io/managed-by
  • app.kubernetes.io/instance
  • app.kubernetes.io/name:

with value modelmesh-controller cause affinity to non existent helm chart

What this PR does / why we need it:

When you deploy the crd with helm (or through argocd/fluxdb) the labels on this predictor CRD are making the CRD shared with non existent helm chart. It adds warning message.

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 #

Type of changes
Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Feature/Issue validation/testing:

Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

  • Test A
    When helm is applied SharedResourceWarning with message:
    CustomResourceDefinition/predictors.serving.kserve.io is part of applications argocd/kserve and modelmesh-controller
    is not there

  • Test B

  • Logs

Special notes for your reviewer:

  1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

  • Have you added unit/e2e tests that prove your fix is effective or that this feature works?
  • Has code been commented, particularly in hard-to-understand areas?
  • Have you made corresponding changes to the documentation?

Release note:


labels: 
- app.kubernetes.io/managed-by 
- app.kubernetes.io/instance
- app.kubernetes.io/name: 

with value modelmesh-controller cause affinity to non existent helm chart

Signed-off-by: Ondrej Trojan <26576371+trojaond@users.noreply.github.com>
@trojaond trojaond changed the title Remove redundant helm chart affinity on predictor CRD Fix bug: Remove redundant helm chart affinity on predictor CRD Feb 27, 2024
Copy link
Member

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@trojaond
Copy link
Contributor Author

/assign @rachitchauhan43

@yuzisun
Copy link
Member

yuzisun commented Mar 3, 2024

/approve

Copy link

oss-prow-bot bot commented Mar 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: terrytangyuan, trojaond, yuzisun

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@oss-prow-bot oss-prow-bot bot added the approved label Mar 3, 2024
@oss-prow-bot oss-prow-bot bot merged commit 56b8fe0 into kserve:master Mar 24, 2024
59 of 60 checks passed
tjandy98 pushed a commit to tjandy98/kserve that referenced this pull request Apr 10, 2024
…e#3481)

Remove redundant helm chart affinity

labels:
- app.kubernetes.io/managed-by
- app.kubernetes.io/instance
- app.kubernetes.io/name:

with value modelmesh-controller cause affinity to non existent helm chart

Signed-off-by: Ondrej Trojan <26576371+trojaond@users.noreply.github.com>
Signed-off-by: tjandy98 <3953059+tjandy98@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants