Open MrLuje opened 3 years ago
@MrLuje thanks for the issue. this does indeed look like an issue with the computed namespaces we operate on when doing a status check. we'll try and get to this one, but if you're feeling up to sending a fix, contributions are of course always welcome.
decreasing priority due to low bandwidth.
Expected behavior
Running skaffold dev should work without issue if I have the required permissions on the deployed namespace
Actual behavior
Skaffold complains about missing permissions at cluster level to check the deployement, whereas it should only check the it at namespace level
Information
Steps to reproduce the behavior
Since the namespace is defined in the release object, I expect it to check the deployement in this namespace and not at cluster level
If a namespace is defined in kubeconfig, it works If a namespace is provided in the skaffold command "skaffold dev -f .\skaffold.cron.yml -n dev", it also works
The issue seems to be occuring during the statusCheck phase, the namespaces property contains "" & "dev", hence making the check at cluster level for ""
https://github.com/GoogleContainerTools/skaffold/blob/250acdff56c17965ee89cf4dde73422764185a0b/pkg/skaffold/kubernetes/status/status_check.go#L141-L154