how to set falcosidekick password webui.user: "admin:admin"

[lumszy]

We make use of argocd and don't want to specify password in manifest. Please, Is there a way around creating and setting a different password for falcosidekick.webui.user by using k8s secrets or other env without specifying or exposing it on the terminal or in manifest? How can we get to support ext auth?

The default admin:admin isn't a good fit for us.

[sambonbonne]

A more general note: we should have the ability to configure sensible informations with secret, like webhook URLs, passwords…

[lumszy]

@sambonbonne I was able to create a k8s secret containing the slack webhook url etc. and then used the key value in value.yaml file to read it in...

config:

-- Existing secret with configuration

existingSecret: ""

My challenge as stated in this issue is still on setting admin password.

[Issif]

Hi,

I'm releasing a new version of falcosidekick-ui after my holidays, begining of September. I'll also update the helm chart and change the method to handle the credentials.

[sambonbonne]

Thanks @lumszy, I did not see the existingSecret key!

[fricka676]

Hello, you used to be able to customize the password through the following method, but now it seems to be invalid and cannot be set in this way

--Set falcosidekick. webui. user="admin: xxxA4567"

[fricka676]

In the end, it's still the default account password

[Issif]

Hello, you used to be able to customize the password through the following method, but now it seems to be invalid and cannot be set in this way

--Set falcosidekick. webui. user="admin: xxxA4567"

I checked and I did a mistake in the last version of the chart, I'll fix it asap.

[shaxiaozz]

Has this issue been updated to the latest helm? I am using the latest helm installation and have the same problem, thank you~

This is my helm install command： helm install falco falcosecurity/falco
--namespace falco --create-namespace
--set ebpf.enabled=true
--set falco.grpc.enabled=true
--set falco.grpc_output.enabled=true
--set falcosidekick.enabled=true
--set falcosidekick.webui.enabled=true
--set falcosidekick.webui.user="admin:admintest"
--set falcosidekick.webui.redis.storageClass=nfs
--set falco.grpc.unixSocketPath=""

This is my helm repository version： CHART：falco-3.7.1 APP VERSION：0.36.0

[Issif]

The falcosidekick chart has been fixed, but it's still updated in the falco's Chart.yaml. As several PR are waiting to be merge for falcosidekic, we'll do it later. It will be quick I hope.

[shaxiaozz]

got it, thank you very much Best Regards,

[Issif]

The falco chart has been updated, use the 3.8.2 to fix this issue.

[shaxiaozz]

extremely grateful

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[riabuz]

@sambonbonne I was able to create a k8s secret containing the slack webhook url etc. and then used the key value in value.yaml file to read it in...

config:

-- Existing secret with configuration

existingSecret: ""

My challenge as stated in this issue is still on setting admin password.

how did you do this exactly? i am struggling to figure out how to reference the specific key within the secret

[poiana]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

[tmsquill]

I would also like to see an example of how to use existingSecret.

[Issif]

I would also like to see an example of how to use existingSecret.

You just have to create the secret with kubectl or else:

kubectl create secret generic falcosidekick-ui -n falco --from-literal=FALCOSIDEKICK_UI_USER=admin:xxxx

Then use the ref in the values.yaml:

...
falcosidekick:
  webui:
    existingSecret: "falcosidekick-ui"
...

That's all

[poiana]

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community. /close

[poiana]

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community. /close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[s7an-it-ez]

FALCOSIDEKICK_UI_USER FALCOSIDEKICK_UI_REDIS_PASSWORD in REDIS_ARGS I pass --reuirepass whatever is in FALCOSIDEKICK_UI_REDIS_PASSWORD but FALCOSIDEKICK_UI_USER points to some default webui_user or smth without having column pass, is that ok? I don't see any exceptions but not sure how to test it. @Issif