-
Notifications
You must be signed in to change notification settings - Fork 64
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(e2e): validate that pulling from an acr registry attached to aks via --attach-acr with karpenter nodes works #457
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/test
Pull Request Test Coverage Report for Build 10512106851Details
💛 - Coveralls |
ca65928
to
aef74f9
Compare
Its failing remotely because the acr name passed in is wrong cd test && CLUSTER_NAME=mc AZURE_ACR_NAME=karpenter go test |
… via --attach-acr with karpenter nodes works
…nge with it disabled
603e6ba
to
c7ee106
Compare
cd test && CLUSTER_NAME=mc AZURE_ACR_NAME=acracr1285317475 go test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couple nits/thoughts on the make commands, but looks good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, minor feedback
fd454bf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
1m 55s nginx Error: Process completed with exit code 1. _-- CI test is failing due to coveralls outage. Just gonna merge as it is. |
@@ -41,14 +41,11 @@ az-mkacr: az-mkrg ## Create test ACR | |||
az-acrimport: ## Imports an image to an acr registry | |||
az acr import --name $(AZURE_ACR_NAME) --source "mcr.microsoft.com/oss/kubernetes/pause:3.6" --image "pause:3.6" | |||
|
|||
az-cleanenv: | |||
az-cleanenv: az-rmnodeclaims-fin ## Deletes a few common karpenter testing resources(pods, nodepools, nodeclaims, aksnodeclasses) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To enforce the order that Charlie was suggesting, one can call make target explicitly in the right place, rather than making it a dependency
… via --attach-acr with karpenter nodes works (#457) * test(e2e): validate that pulling from an acr registry attached to aks via --attach-acr with karpenter nodes works * fix: ci * test: ci * fix: crd validation breaks on local so accidentally committed the change with it disabled * fix: passing in azure acr name from env rather than using makefile default * fix: ci again? * fix: nit comments addressed * test: only provisioning one pod
Fixes #
Description
As part of the efforts to fix 1.30 bootstrap we removed a flag that removes functionality for out of tree providers. One of the side affects of this is that ACR Pull will not work in the same way. We needed a way to validate this image pull works in a reproducible and consistent way.
This test suite is that. Currently it has to be ran locally to target specific k8s versions so a nice followup at lower priority would be to add the ability to run our e2es against a specific k8s version.
How was this change tested?
Does this change impact docs?
Release Note