One reason this happens is that the k8s account is not configured for the namespace being deployed to. Check the .hal/config for the account and namespaces the account is configured for.
If you are using OES, you can check it in settings->Accounts.
Modified on: Tue, 15 Dec, 2020 at 5:46 AM
One reason this happens is that the k8s account is not configured for the namespace being deployed to. Check the .hal/config for the account and namespaces the account is configured for.
If you are using OES, you can check it in settings->Accounts.
Did you find it helpful? Yes No
Send feedback