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
Add BMH annotation keys to docs #5444
Add BMH annotation keys to docs #5444
Conversation
Previously we said which fields could be set using annotations, but didn't document the annotation keys
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carbonin 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 |
@carbonin: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@@ -160,10 +160,17 @@ In case that the Bare Metal Operator is installed, the Baremetal Agent Controlle | |||
|
|||
- Find the right pairs of BMH/Agent using their MAC addresses | |||
- Set the Image.URL in the BMH copying it from the InfraEnv's status. |
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.
Is this even still true since converged?
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.
(unrelated to PR)
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.
No, but there's a specific section for converged.
/lgtm |
Previously we said which fields could be set using annotations, but didn't document the annotation keys
Previously we said which fields could be set using annotations, but didn't document the annotation keys
Previously we said which fields could be set using annotations, but didn't document the annotation keys
Previously we said which fields could be set using annotations, but didn't document the annotation keys
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist