Skip to content

Set hardened Security Context for Kibana elastic-internal-init init container #8827

@barkbay

Description

@barkbay

Kibana init container elastic-internal-init has no security context set.

I think it's because of an oversight here.

We should also adjust the unit test TestNewInitContainer in which tt.args.setDefaultSecurityContext is actually not used.

Metadata

Metadata

Assignees

Labels

>bugSomething isn't working

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