-
Notifications
You must be signed in to change notification settings - Fork 8
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
e2e: add a test for checking AKS upstream #939
Conversation
b8059ee
to
8fc4293
Compare
Note that the boilerplate of manually adding the |
54b0fb1
to
9985321
Compare
faad72e
to
71b3501
Compare
Due to |
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, just a few nits
b06a87e
to
9edd55a
Compare
New successful run here |
two jobs indentation :( add forgotten permissions
remove accidental inclusion of t
bdd1fc3
to
de49a8e
Compare
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, let's merge it :)
withExtensions = with final.azure-cli.extensions; [ | ||
aks-preview | ||
confcom |
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.
Is this used anywhere in the end? Looks like we are installing the cli via apt.
Add a test that checks if something in azure upstream is broken by deploying a simple container with the
kata-cc-isolation
runtime class. You can view a successful workflow run here.