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

feat: remove PersistentVolumeClaim annotation volume.kubernetes.io/selected-node #4943

Merged
merged 1 commit into from
May 16, 2024

Conversation

a7i
Copy link
Contributor

@a7i a7i commented May 15, 2024

What type of PR is this?

/kind bug

What this PR does / why we need it:

As my colleague @jklaw90 discovered that selected-node is for the node that volume is mounted on. If this node doesn't exist, then it is never removed. See upstream issue: kubernetes/kubernetes#100485

we should also remove this field since it's irrelevant, given that node names are likely not going to be the same.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

karmada-controller-manager: remove cluster specific `PersistentVolume` annotation `volume.kubernetes.io/selected-node`

@karmada-bot karmada-bot added the kind/bug Categorizes issue or PR as related to a bug. label May 15, 2024
@karmada-bot karmada-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 15, 2024
@a7i
Copy link
Contributor Author

a7i commented May 15, 2024

@a7i a7i force-pushed the retain-pv-selected-node branch from cb5edb4 to 384afd4 Compare May 15, 2024 21:21
@a7i a7i changed the title feat: retain PersistentVolumeClaim annotation `volume.kubernetes.io… feat: retain PersistentVolumeClaim annotation volume.kubernetes.io/selected-node May 15, 2024
@a7i a7i changed the title feat: retain PersistentVolumeClaim annotation volume.kubernetes.io/selected-node feat: remove PersistentVolumeClaim annotation volume.kubernetes.io/selected-node May 15, 2024
Copy link
Member

@RainbowMango RainbowMango left a comment

Choose a reason for hiding this comment

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

/approve

Leave LGTM to @XiShanYongYe-Chang to take another look.

@karmada-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

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

@karmada-bot karmada-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 16, 2024
Copy link
Member

@XiShanYongYe-Chang XiShanYongYe-Chang left a comment

Choose a reason for hiding this comment

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

Thanks~
/lgtm

@karmada-bot karmada-bot added the lgtm Indicates that a PR is ready to be merged. label May 16, 2024
@karmada-bot karmada-bot merged commit fbb6411 into karmada-io:master May 16, 2024
12 checks passed
@a7i a7i deleted the retain-pv-selected-node branch May 16, 2024 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants