-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature/vsha 547 #55
Feature/vsha 547 #55
Conversation
You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good other than the changelog nit. I can help this get shepherded through once we get a second approval.
Thanks! I appreciate the help with the versioning, that was confusing me. |
Kudos, SonarCloud Quality Gate passed!
|
No problem. In theory we follow the process defined here: Although there are various deviations from it. |
Summary and Scope
Add Helm chart content and code to enable the logic for setting the architecture and type when generating the iPXE binary that has been latent in the code for quite a while. This is needed to used cms-ipxe on vShasta because vShasta uses KPXE binaries not EFI.
Backward compatible change.
Issues and Related PRs
Testing
Tested on:
Test description:
Installed on vShasta v2 system and verified that I could build a KPXE binary using cray-ipxe. Also verified that the chart with no special customizations creates a cray-ipxe that builds an EFI / x86 binary.
Risks and Mitigations
There are no known risks or issues with this change.
Pull Request Checklist