Add documentation for skip contact check for bmc machines

[rajeshvenkata]

Issue #, if available:

Documentation added/planned (if applicable):
We have added support to skip bmc connectivity check for faulty bmc machines. In this PR, I am updating documentation for the skip BMC connectivity check feature in the Bare Metal upgrades guide. Users can now label faulty BMC machines to
prevent them from blocking cluster upgrades.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from rajeshvenkata. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• docs/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.01%. Comparing base (0841771) to head (935f458).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #10366   +/-   ##
=======================================
  Coverage   70.01%   70.01%           
=======================================
  Files         680      680           
  Lines       41755    41755           
=======================================
  Hits        29236    29236           
  Misses      10722    10722           
  Partials     1797     1797           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rajeshvenkata]

/cherry-pick release-0.24

[eks-distro-pr-bot]

@rajeshvenkata: once the present PR merges, I will cherry-pick it on top of release-0.24 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.24

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.

[rajeshvenkata]

/cherry-pick release-0.23

[eks-distro-pr-bot]

@rajeshvenkata: once the present PR merges, I will cherry-pick it on top of release-0.23 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.23

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.

[rajeshvenkata]

/hold

[snarkychef]

/lgtm

[snarkychef]

/lgtm

[rajeshvenkata]

/cherry-pick release-0.23

[rajeshvenkata]

/cherry-pick release-0.24

[eks-distro-pr-bot]

@rajeshvenkata: new pull request created: #10379

In response to this:

/cherry-pick release-0.24

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.

[eks-distro-pr-bot]

@rajeshvenkata: new pull request created: #10380

In response to this:

/cherry-pick release-0.23

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.

[eks-distro-pr-bot]

@rajeshvenkata: new pull request could not be created: failed to create pull request against aws/eks-anywhere#release-0.24 from head eks-distro-pr-bot:cherry-pick-10366-to-release-0.24: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for eks-distro-pr-bot:cherry-pick-10366-to-release-0.24."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherry-pick release-0.24

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.

[eks-distro-pr-bot]

@rajeshvenkata: new pull request could not be created: failed to create pull request against aws/eks-anywhere#release-0.23 from head eks-distro-pr-bot:cherry-pick-10366-to-release-0.23: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for eks-distro-pr-bot:cherry-pick-10366-to-release-0.23."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherry-pick release-0.23

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.