Skip to content

Conversation

@alicefr
Copy link

@alicefr alicefr commented Oct 20, 2025

In order to support new clevis pin, either they need to be added each time in the hardcoded list of pins or ignition can allow any name for the pin. This is required in order to enable the clevis trustee pin used for confidential clusters.

In order to support new clevis pin, either they need to be added each
time in the hardcoded list of pins or ignition can allow any name for
the pin. This is required in order to enable the clevis trustee pin used
for confidential clusters.

Signed-off-by: Alice Frosi <afrosi@redhat.com>
@alicefr
Copy link
Author

alicefr commented Oct 20, 2025

/cc @travier @jlebon

@alicefr alicefr closed this Oct 20, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request modifies the configuration validation to allow for arbitrary custom Clevis pin names. The change is motivated by the need to support new pins, such as the 'trustee' pin, without having to update a hardcoded list. The implementation correctly removes the switch statement that enforced a whitelist of pin names in config/v3_6_experimental/types/clevis.go. The corresponding unit test in config/v3_6_experimental/types/clevis_test.go is also updated to reflect that a previously unknown pin name is now considered valid. The changes are straightforward, correct, and align with the pull request's objective. I have no further comments.

@alicefr alicefr reopened this Oct 20, 2025
@alicefr
Copy link
Author

alicefr commented Oct 20, 2025

This PR has been created upon the discussion in #2120 (comment)

@alicefr alicefr closed this Oct 20, 2025
@alicefr alicefr reopened this Oct 20, 2025
@alicefr
Copy link
Author

alicefr commented Oct 20, 2025

How do I fix the release notes?

},
at: path.New("", "pin"),
out: errors.ErrUnknownClevisPin,
out: nil,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we add a negative test as well please?

Copy link
Author

Choose a reason for hiding this comment

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

There are already existing tests covering when the name is empty, so I'm not sure what else we should check. This PR is relaxing the name checking to arbitrarily non-empty string

@yasminvalim
Copy link
Contributor

yasminvalim commented Oct 30, 2025

How do I fix the release notes?

@alicefr you need to write a simple release notes on ignition/docs/release-notes.md about your change. 😸

@yasminvalim
Copy link
Contributor

Hey, @alicefr! Thanks for working on this 🫂
LGTM, just need a release notes :)

Signed-off-by: Alice Frosi <afrosi@redhat.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.

3 participants