add unit tests for hostname node.status.addresses#125809
Conversation
|
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The DetailsInstructions 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. |
|
big +1 for getting test coverage in place for all the combinations of explicit / auto-detected --node-ip, explicit / auto-detected --hostname-override, and external / no cloud provider. Can you see what these do prior to #121028 and prior to #124516? I think (but have not had time to dig in and verify) that #124516 regressed how kubelet requests CSRs on startup in some configurations (#124554 (comment)) and I'm super wary of locking in that unreleased behavior in a unit test. |
|
Oh, I misread the PR :) I thought this was testing kubelet address reporting behavior. |
will follow up on that, this is just to be sure the hostname behavior is tested so we can prevent regressions |
|
this looks good to me, i am unfamiliar with the error coming from pull-kubernetes-integration, is that related to this change? |
does not seem related
/test pull-kubernetes-integration |
|
/assign @cheftako can you please approve? |
|
/lgtm Thanks for adding this Antonio |
|
LGTM label has been added. DetailsGit tree hash: 36ccc27b632dbab0afd8744c6b65ddeb74b7a840 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, cheftako The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/kind cleanup
This unit tests helps to ensure the existing behavior of the node controller on the cloud provider does not change and to avoid regressions.
hostnameaddress type and the external cloud provider also provides it, the value is overridenhostnameaddress type and the external cloud provider does not provide it, the value from the Node object is used/sig cloud-provider
Ref: #124516
/assign @danwinship @liggitt @cheftako @elmiko