You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the test steps call ${KUBECTL} whenever kubectl commands are executed. However, when asserting deletion, kubectl is used instead, which leads to failures if kubectl is not in $PATH.
How can we reproduce it?
Examine logs closely; observe lines like
kubectl wait <something> --for=delete <etc>
during the Delete step.
What environment did it happen in?
Uptest Version: 1.1.2
Chainsaw Version: 0.2.0
Reasons for the undesired behavior:
Everywhere in templates, ${KUBECTL} is called explicitly, except for the assertion step in the Delete template, where Chainsaw's wait directive is used.
What happened?
All the test steps call
${KUBECTL}
whenever kubectl commands are executed. However, when asserting deletion,kubectl
is used instead, which leads to failures ifkubectl
is not in$PATH
.How can we reproduce it?
Examine logs closely; observe lines like
during the Delete step.
What environment did it happen in?
Reasons for the undesired behavior:
Everywhere in templates,
${KUBECTL}
is called explicitly, except for the assertion step in the Delete template, where Chainsaw'swait
directive is used.Chainsaw, unfortunately, has
kubectl
hardcoded.The text was updated successfully, but these errors were encountered: