Skip to content

add unit tests for hostname node.status.addresses#125809

Merged
k8s-ci-robot merged 1 commit into
kubernetes:masterfrom
aojea:cloud_hostname
Jul 17, 2024
Merged

add unit tests for hostname node.status.addresses#125809
k8s-ci-robot merged 1 commit into
kubernetes:masterfrom
aojea:cloud_hostname

Conversation

@aojea

@aojea aojea commented Jun 30, 2024

Copy link
Copy Markdown
Member

/kind cleanup

NONE

This unit tests helps to ensure the existing behavior of the node controller on the cloud provider does not change and to avoid regressions.

  1. If the Node object contains a hostname address type and the external cloud provider also provides it, the value is overriden
  2. If the Node object contains a hostname address 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

@k8s-ci-robot k8s-ci-robot added the release-note-none Denotes a PR that doesn't merit a release note. label Jun 30, 2024
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Jun 30, 2024
@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 30, 2024
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines 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.

Details

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.

@k8s-ci-robot k8s-ci-robot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jun 30, 2024
@liggitt

liggitt commented Jun 30, 2024

Copy link
Copy Markdown
Member

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.

@liggitt

liggitt commented Jun 30, 2024

Copy link
Copy Markdown
Member

Oh, I misread the PR :)

I thought this was testing kubelet address reporting behavior.

@aojea

aojea commented Jun 30, 2024

Copy link
Copy Markdown
Member Author

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.

will follow up on that, this is just to be sure the hostname behavior is tested so we can prevent regressions

@danwinship

danwinship commented Jul 1, 2024

Copy link
Copy Markdown
Contributor

I think (but have not had time to dig in and verify) that #124516 regressed how kubelet requests CSRs on startup in some configurations

124516 is supposed to just be bringing back the pre-1.29 behavior. I don't think that's where the regression came from.

EDIT: ok, it is. Fixed by #125813

@elmiko

elmiko commented Jul 10, 2024

Copy link
Copy Markdown
Contributor

this looks good to me, i am unfamiliar with the error coming from pull-kubernetes-integration, is that related to this change?

@aojea

aojea commented Jul 12, 2024

Copy link
Copy Markdown
Member Author

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

{Failed; === RUN TestWebhookConverterWithWatchCache

/test pull-kubernetes-integration

@aojea

aojea commented Jul 17, 2024

Copy link
Copy Markdown
Member Author

/assign @cheftako

can you please approve?

@cheftako

Copy link
Copy Markdown
Member

/lgtm
/approve

Thanks for adding this Antonio

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 17, 2024
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 36ccc27b632dbab0afd8744c6b65ddeb74b7a840

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[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

Details Needs approval from an approver in each of these files:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 17, 2024
@k8s-ci-robot k8s-ci-robot merged commit ef8d67f into kubernetes:master Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/cloudprovider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants