Skip to content

Conversation

llamerada-jp
Copy link
Contributor

@llamerada-jp llamerada-jp commented Mar 21, 2025

We have found a limitation that the pod cannot be started when nodeName is specified. This behavior is due to kube scheduler, and cannot be fixed in TopoLVM. Therefore, we will create faq.md and add a note.

@llamerada-jp llamerada-jp requested a review from a team as a code owner March 21, 2025 08:27
Copy link
Contributor

@daichimukai daichimukai left a comment

Choose a reason for hiding this comment

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

In my understanding, this is more of a natural consequence of the specifications of Kubernetes itself rather than a limitation of TopoLVM. I believe that addressing this in an FAQ or similar resource would be appropriate. What do you think?

Thus, if a pod consumes a restored/cloned PV having a different storage class from the original PV, this pod will not get scheduled if the StorageClass contents differ from the source StorageClass (e.g. by using a different device class).

## The Pod does not start when nodeName is specified in the Pod spec
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
## The Pod does not start when nodeName is specified in the Pod spec
## The Pod does not start when nodeName is specified in the Pod spec

pluser
pluser previously approved these changes Mar 24, 2025
@llamerada-jp llamerada-jp force-pushed the lilmitation-node-name branch 2 times, most recently from c617e22 to 9b34e6c Compare March 26, 2025 09:37
We have found a limitation that the pod cannot be started when
nodeName is specified. This behavior is due to kube scheduler,
and cannot be fixed in TopoLVM. Therefore, we will create faq.md
and add a note.

Signed-off-by: Yuji Ito <llamerada.jp@gmail.com>
@llamerada-jp llamerada-jp force-pushed the lilmitation-node-name branch from 9b34e6c to d2bdbf9 Compare April 2, 2025 00:56
@llamerada-jp llamerada-jp merged commit 2fd6894 into main Apr 3, 2025
8 checks passed
@llamerada-jp llamerada-jp deleted the lilmitation-node-name branch April 3, 2025 00:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants