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

aks command invoke: evalsymlink failure on '/command-files/https:/github.com/ #189

Closed
bhandariakshay1601 opened this issue Jul 11, 2022 · 3 comments
Labels
question 🙋 Further information is requested triage 💭 Need triage to replicate or identify right fix

Comments

@bhandariakshay1601
Copy link

Related command

az aks command invoke --resource-group <> --name <> --command "kubectl kustomize ." --file

Describe the bug
When trying to deploy aks periscope via aks command invoke, I am seeing the following error
Error: rawResources failed to read Resources: Load from path https://github.com/azure/aks-periscope//deployment/base?ref=v0.9 failed: evalsymlink failure on '/command-files/https:/github.com/azure/aks-periscope/deployment/base?ref=v0.9' : lstat /command-files/https:: no such file or directory

To Reproduce

If we run this command on any aks cluster
az aks command invoke --resource-group <> --name <> --command "kubectl kustomize ." --file

we will be able to reproduce
kustomization.YAML

resources:

https://github.com/azure/aks-periscope//deployment/base?ref=v0.9
images:

name: periscope-linux
newName: mcr.microsoft.com/aks/periscope
newTag: 0.0.9
name: periscope-windows
newName: mcr.microsoft.com/aks/periscope-win
newTag: 0.0.9
secretGenerator:

name: azureblob-secret
behavior: replace
literals:
AZURE_BLOB_ACCOUNT_NAME=<>
AZURE_BLOB_CONTAINER_NAME=<>
AZURE_BLOB_SAS_KEY=?<>
Expected behavior

COmmand should have been successful

Environment summary

Additional context

@Tatsinnit Tatsinnit added the triage 💭 Need triage to replicate or identify right fix label Jul 13, 2022
@peterbom
Copy link
Contributor

@bhandariakshay1601: thank you for logging the issue!

This looks very much like an incompatibility with the kubectl version (see similar issue).

Would you be able to run kubectl version and upgrade if it's below 1.21? I'm hopeful that would resolve the error.

We have been intending to update our README to call out the version dependency, so thank you for the reminder!

@Tatsinnit Tatsinnit added the question 🙋 Further information is requested label Jul 13, 2022
@Tatsinnit
Copy link
Member

Thank you @peterbom for updating and taking a look, and thank you so much @bhandariakshay1601 for opening this, please let us know if there is anything else you want to be covered? otherwise the update of kubectl should fix the issue, thanks again

@Tatsinnit
Copy link
Member

💡Closing this issue for now, please let us know if there is anything else is in need and we can reopen this issue. Thank you so much all. 🙏☕️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question 🙋 Further information is requested triage 💭 Need triage to replicate or identify right fix
Projects
None yet
Development

No branches or pull requests

3 participants