Skip to content

feat(source): add resouce labels for nodes#5509

Merged
k8s-ci-robot merged 1 commit intokubernetes-sigs:masterfrom
gofogo:chore-source-node-add-resource-label
Jun 9, 2025
Merged

feat(source): add resouce labels for nodes#5509
k8s-ci-robot merged 1 commit intokubernetes-sigs:masterfrom
gofogo:chore-source-node-add-resource-label

Conversation

@ivankatliarchuk
Copy link
Member

@ivankatliarchuk ivankatliarchuk commented Jun 8, 2025

What does it do ?

This is a follow-up for PR #5498

Motivation

  • add resource labels for node source
    • use cases
      • visibility, as currently difficult to debug why node enpoint is not accessible, the node could be unscedulable, but there is no way to trace DNS back to a node
      • visibility, it clearly shows that endpoint is created from the node

The more standart we have config accross different sources, easier to maintain them

More

  • Yes, this PR title follows Conventional Commits
  • Yes, I added unit tests
  • Yes, I updated end user documentation accordingly

Signed-off-by: ivan katliarchuk <ivan.katliarchuk@gmail.com>
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 8, 2025
@k8s-ci-robot k8s-ci-robot requested a review from mloiseleur June 8, 2025 07:50
@k8s-ci-robot k8s-ci-robot requested a review from szuecs June 8, 2025 07:50
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 8, 2025
@mloiseleur mloiseleur changed the title chore(source/node): added resouce labels for nodes feat(source): add resouce labels for nodes Jun 8, 2025
@mloiseleur
Copy link
Collaborator

It looks like more a feat than a chore to me :).
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 8, 2025
@ivankatliarchuk
Copy link
Member Author

Yeah. Need to be better with feat/chore things

@ivankatliarchuk
Copy link
Member Author

ivankatliarchuk commented Jun 9, 2025

Tested on dummy cluster with nodes that have quite lengty names

eks nodes
Screenshot 2025-06-09 at 11 56 14

Screenshot 2025-06-09 at 11 51 15 Screenshot 2025-06-09 at 11 52 01

@ivankatliarchuk
Copy link
Member Author

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ivankatliarchuk

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 Jun 9, 2025
@ivankatliarchuk
Copy link
Member Author

/test pull-external-dns-unit-test

@ivankatliarchuk
Copy link
Member Author

/retest-required

@k8s-ci-robot k8s-ci-robot merged commit 28cac12 into kubernetes-sigs:master Jun 9, 2025
16 checks passed
@ivankatliarchuk ivankatliarchuk deleted the chore-source-node-add-resource-label branch June 9, 2025 11:13
ivankatliarchuk added a commit to gofogo/k8s-sigs-external-dns-fork that referenced this pull request Jun 10, 2025
* master:
  test(source): fix flaky test (kubernetes-sigs#5514)
  chore(source/node): added resouce labels for nodes (kubernetes-sigs#5509)
  chore(deps): bump the dev-dependencies group across 1 directory with 14 updates (kubernetes-sigs#5511)
  fix(ovh): correct handling of records deletion (kubernetes-sigs#5450)
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. source

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants