Skip to content

Falcosidekick may use outdated token #483

Description

@marwinski

What happened:

The falcosidekick token is statically injected into the falcosidekick configuration when the pod starts (for the logging use case). If, in the remote situation that the pod is not reconciled and restarted within one month the token would be invalid and events would not get propagated.

What you expected to happen:

Events always to get propagated.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

Environment:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions