Can not start in AWS IAM environment about kubeshark HOT 7 CLOSED

HI @danishnawab
Thanks for reaching out.
Mizu tap creates an "agent" pod inside your cluster, in order to access the web ui mizu CLI tries to create k8s proxy or port forward. So the user which running the CLI need to have certain permissions in the cluster like get pod/service. Just wanted to double check that your IAM user have these permissions in a newly created namespace like "mizu"?

from kubeshark.

@IgorGov No, my user doesn't have access to the mizu namespace, not out of the box.
Access within our organization is limited to the namespaces we deploy our stuff on. And, mizu is not one of those.
Could there be a way by which mizu could run in such environments? I suppose there would be others with a similar authentication setup.
Perhaps mizu could instead start the agent in the existing namespaces instead of a new namespace?

from kubeshark.

Mizu have the ability to be deployed (and created needed resources) to an existing namespace, you can use the "mizu-resources-namespace" flag:
./mizu tap --set mizu-resources-namespace=<namespace for k8s resource to be deployed> -n <the same namespace>

Notice that you won't be able to deploy to namespace "A" and sniff traffic from namespace "B".

Let me know if that helps

from kubeshark.

So deploying mizu in one of the existing services worked to the point that the server could come up and the traffic viewer was loaded in my browser, however, I didn't see any traffic.
Looking at the logs, I could see the following statements:

[2022-02-08T23:46:31.669+0100] DEBUG ▶ error while getting kubernetes server version, err: Get "https://<redacted>:443/version?timeout=32s": getting credentials: exec: executable aws-iam-authenticator failed with exit code 1 ▶ [68653 provider.go:1149 GetKubernetesVersion]
[2022-02-08T23:46:31.670+0100] ERROR ▶ Get "https://<redacted>:443/version?timeout=32s": getting credentials: exec: executable aws-iam-authenticator failed with exit code 1 ▶ [68653 common.go:94 handleKubernetesProviderError]

At first, I assumed that my IAM user doesn't have the access rights to query the k8s version, but then I tried executing kubectl version and it successfully listed both the client and the server versions.

from kubeshark.

can you please run the command with flag "--set dump-logs=true", it should generate a zip file with all mizu logs (cli, server and tappers). The command should look like:
../mizu tap --set mizu-resources-namespace=<ns> -n <ns> --set dump-logs=true

Can you confirm that CLI detects pods to tap? the output should look like:

Can you confirm that mizu tapper pods are up and running? see the highlighted pods:

from kubeshark.

This issue is stale because it has been open for 30 days with no activity.

from kubeshark.

This issue was closed because it has been inactive for 14 days since being marked as stale.

from kubeshark.