[occm] Add container-level securityContext to Helm chart

[zwindler]

[occm] Add container-level securityContext to Helm chart

What this PR does / why we need it:

Adds support for container-level securityContext configuration in the openstack-cloud-controller-manager Helm chart.

Previously, only pod-level podSecurityContext was configurable. This allows users to set container-specific security settings.

Which issue this PR fixes(if applicable):

N/A

Special notes for reviewers:

The change adds a new securityContext field in values.yaml and applies it to the main container in the DaemonSet template. The default is an empty object {} to maintain backward compatibility.

Release note:

[openstack-cloud-controller-manager] Add container-level securityContext configuration support to Helm chart

[k8s-ci-robot]

Welcome @zwindler!

It looks like this is your first PR to kubernetes/cloud-provider-openstack 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/cloud-provider-openstack has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @zwindler. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[dulek]

/ok-to-test

Looks like you need to bump the version of the chart to indicate you made changes.

[zwindler]

Thanks for the heads up, I fixed it :)

[kayrus]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kayrus

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [kayrus]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment