-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
tests: Improve the kbs_k8s_delete function #9423
Conversation
@wainersm besides the pod, do you want me to verify the deployment and the configmaps? |
Hi @GabyCT ! Hey, thanks for working on it!
Notice that currently we only have support for the AKS ingress, but after the merge of #9273 we will have the nodeport too. The AKS"s ingress will install daemonsets too IIRC and we will need to check they were over. The nodeport ingress model will only deploy a service which I don"t believe we should check it is deleted. |
42ab710
to
f5d1695
Compare
f5d1695
to
fb4c359
Compare
This PR improves the kbs_k8s_delete function to verify that the resources were properly deleted for baremetal environments. Fixes kata-containers#9379 Signed-off-by: Gabriela Cervantes <[email protected]>
@wainersm I tested this PR on a baremetal environment and seems working as it verifies the nodeport and aks
After running the PR, I verify that both nodeport and aks was gone on the baremetal |
/test |
This PR improves the kbs_k8s_delete function to verify that the resources were properly deleted for baremetal environments.
Fixes #9379