Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test(make): add taint node make command #234

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

charliedmcb
Copy link
Collaborator

Fixes #

Description
I've found I've been wanting this make command myself, so adding one to the file.

How was this change tested?
Nothing additional
*

Does this change impact docs?

  • Yes, PR includes docs updates
  • Yes, issue opened: #
  • No

Release Note

NONE

@charliedmcb charliedmcb marked this pull request as ready for review March 28, 2024 22:30
@coveralls
Copy link

Pull Request Test Coverage Report for Build 8474483294

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 97.716%

Totals Coverage Status
Change from base Build 8428081342: 0.0%
Covered Lines: 35591
Relevant Lines: 36423

💛 - Coveralls

@charliedmcb charliedmcb merged commit 06a9b60 into main Mar 28, 2024
10 checks passed
@charliedmcb charliedmcb deleted the charliedmcb/taintNodesMakeCommand branch March 28, 2024 22:51
@@ -232,6 +232,9 @@ az-rmnodeclaims-fin: ## Remove Karpenter finalizer from all nodeclaims (use with
az-rmnodeclaims: ## kubectl delete all nodeclaims; don't wait for finalizers (use with care!)
kubectl delete --wait=false nodeclaims --all

az-taintnodes: ## Run e2etests
kubectl taint nodes CriticalAddonsOnly=true:NoSchedule --all --overwrite
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have use cases where this is not constrained to system nodepool? If not - should we target it explicitly with selector?

Copy link
Collaborator

@Bryce-Soghigian Bryce-Soghigian Mar 28, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I use this sometiems when running perf test, but not all of the nodes have scaled down I just want to launch a bunch of small instances to test something.

So tainting all nodes is useful

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe tainting by label could be a second command?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a fair idea. I've been running it right after cluster creation. However, it would be helpful to ensure it only targets system nodepool. I'll look at doing that.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will need a follow up PR though as I already completed

@@ -232,6 +232,9 @@ az-rmnodeclaims-fin: ## Remove Karpenter finalizer from all nodeclaims (use with
az-rmnodeclaims: ## kubectl delete all nodeclaims; don't wait for finalizers (use with care!)
kubectl delete --wait=false nodeclaims --all

az-taintnodes: ## Run e2etests
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment is wrong

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thx for the catch. Got a little eager on the completion. Another reason for a follow up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants