Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run hazelcast in restricted Pod Security Standard namespace #456

Open
focdanisch opened this issue Jan 27, 2025 · 0 comments
Open

Run hazelcast in restricted Pod Security Standard namespace #456

focdanisch opened this issue Jan 27, 2025 · 0 comments

Comments

@focdanisch
Copy link

Hello,

this issue refers to the closed issue #425. That issue was opened and immediately closed as completed. But I do not see any changes in the mentioned chart templates. If I look at the first and second usage of .Values.securityContext.enabled, I see that there are variables, that can be overridden by the user. But there seems to be no obvious way to add custom settings to the securityContext. When I deploy the chart with the default values into a "normal", unrestricted namespace (without any labels), this works as expected. But if I try to set the Pod Security Standard on this namespace to restricted using the recommended command

kubectl label --dry-run=server --overwrite ns testing pod-security.kubernetes.io/enforce=restricted

I get a warning saying:

Warning: demo-hazelcast-0 (and 2 other pods): seccompProfile

This is, because the securityContext is missing the required seccompProfile setting. Now issue #425 unfortunately does not provide any further information how that can be accomplished. I would be required to add something like

template:
  spec:
    containers:
      securityContext:
        seccompProfile:
          type: RuntimeDefault

to the existing settings, but the current charts seems to not provide such an enhancement. Could you please elaborate how I can add the seccompProfile-setting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant