Skip to content

Conversation

@Yu-Jack
Copy link
Contributor

@Yu-Jack Yu-Jack commented Jan 26, 2026

Problem:

Solution:

I added the following feature

  1. Adde device filter, which we didn't have before.

  2. Loading config map to filter the blockdevice and select candidates for auto provision.

    1. Add config map resource under deploy folder. Please check deploy/charts/harvester-node-disk-manager/values.yaml for more details.

    2. Set exclude filter and auto provision every time when scanner starts. It's useful when config map is changed. But, I don't think we need to notify scanner to scan again when the config map is changed. Just one way direction is enough.

  3. Fallback mechanism. If config map doesn't exist, it directly uses the env variables. This is just for the upgrade if the upgrade fails.

Related Issue:
harvester/harvester#5059

Test plan:

Signed-off-by: Jack Yu <jack.yu@suse.com>
Signed-off-by: Jack Yu <jack.yu@suse.com>
Signed-off-by: Jack Yu <jack.yu@suse.com>
Signed-off-by: Jack Yu <jack.yu@suse.com>
Signed-off-by: Jack Yu <jack.yu@suse.com>
Signed-off-by: Jack Yu <jack.yu@suse.com>
Signed-off-by: Jack Yu <jack.yu@suse.com>
@Yu-Jack Yu-Jack self-assigned this Jan 26, 2026
@Yu-Jack Yu-Jack changed the title Harv 5059 feat: support filter list Jan 26, 2026
Signed-off-by: Jack Yu <jack.yu@suse.com>
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.

1 participant