Parameter `accessKey` is required to connect to armosec.io dashboard (and not `access-key`) about kubescape HOT 4 CLOSED

HI @ioannisgk,

Thanks for raising this issue.

We have opened a PR to fix the access key parameters in the values file. (kubescape/helm-charts#387)

As for the first issue, we'd like to have a session with you if possible so we can understand why it happens since it was not reproduced when I checked it.

from kubescape.

@ioannisgk

After checking with engineering team we might have a better understanding of the issue. For each user which signs up an access key should be generated by default but for your account this was not the case, and that would be the reason for the missing access key in the command that showed up in the UI.
We have recently fixed a bug in the ARMO platform related to access key generation but it only applies for new sign ups.

A few questions:

• Did you sign up for the ARMO platform recently? If not, when (approximately)?
• Did you encounters any errors during sign up?
• Did you connect your cluster right after signing up?

from kubescape.

@amirmalka

Thank you for the explanation. Regarding your questions:

• I signed up for ARMO on 23rd of November 2023
• I encountered no errors during sign up
• After signing up, I used only the account parameter and I could see all the data in ARMO platform (the connection to the cluster was successful)

A few days ago I used the Helm chart v1.18.1 and I saw the error, thus finding out that I had to use the accessKey parameter to make the connection work.

from kubescape.

Thanks @ioannisgk
The bug has been solved in ARMO platform and a new helm chart was released with the fix for the access key value.

from kubescape.