Healthcheck annotations incorrectly documented as limited to NLB

[samuel-esp]

What happened:

Inside the recently pushed commit for documentation (#1163), healthcheck annotations are declared to be valid only for NLB while, reading the code, they are also valid for the Classic ELB

Anything else we need to know?:

This issue is partially related to #1181. The documention will be a bit misleading until the PR that solves that issue (#1182) is merged since specifying a lowercase value for the protocol annotation ("http" or "tpc") will create a wrong configuration on the AWS ELB

/kind bug

[k8s-ci-robot]

This issue is currently awaiting triage.

If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[mtulio]

thanks for reporting, @samuel-esp . I just open the PR #1199 for the current state. PTAL

[mtulio]

thanks for reporting, @samuel-esp . I just open the PR #1199 for the current state. PTAL

I see #1184 was created. Closing as duplicated.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale