Skip to content
This repository has been archived by the owner on Feb 20, 2024. It is now read-only.

Add possibility to set securityContext for Kafka and Zookeeper containers #473

Merged

Conversation

sturman
Copy link
Contributor

@sturman sturman commented Oct 27, 2020

What changes were proposed in this pull request?

Added possibility to include securityContext for Zookeeper and Kafka containers

How was this patch tested?

  • set

    cp-kafka:
      securityContext:
        runAsUser: 0
        runAsGroup: 0

    and

    cp-zookeeper:
      securityContext:
        runAsUser: 0
        runAsGroup: 0

    in values.yaml

  • helm template kafka ./ > some.yaml
  • find securityContext in some.yaml

  • verified securityContext is set according to values in values.yaml

@ghost
Copy link

ghost commented Oct 27, 2020

It looks like @sturman hasn't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement here.

Once you've signed reply with [clabot:check] to prove it.

Appreciation of efforts,

clabot

@sturman
Copy link
Contributor Author

sturman commented Oct 27, 2020

[clabot:check]

@ghost
Copy link

ghost commented Oct 27, 2020

@confluentinc It looks like @sturman just signed our Contributor License Agreement. 👍

Always at your service,

clabot

@gAmUssA gAmUssA merged commit 7b15e2a into confluentinc:master Oct 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants