feat: add hostPID for linux daemonset container

[jamesalford]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind test
/kind failing-test
/kind flake

/kind feature

What this PR does / why we need it:
Adds the ability to add hostPID to the container spec for linux daemonset. This is used to execute scripts in init containers that modify the host storage

~/go/src/github.com/kubernetes-sigs/sig-storage-local-static-provisioner/helm# ../hack/update-generated.sh
*** IMPORTANT NOTE ***
This script is used to update generated yaml files from helm values
automatically. It does not validate generated yaml files. Please check to make
sure generated files are what you expected.
*** IMPORTANT NOTE ***
====== HELM v3 ========
Generating with helm v3.10.1 generated_examples/additional-volumes.yaml from examples/additional-volumes.yaml
Generating with helm v3.10.1 generated_examples/baremetal-affinity.yaml from examples/baremetal-affinity.yaml
Generating with helm v3.10.1 generated_examples/baremetal-cleanbyjobs.yaml from examples/baremetal-cleanbyjobs.yaml
Generating with helm v3.10.1 generated_examples/baremetal-default-storage.yaml from examples/baremetal-default-storage.yaml
Generating with helm v3.10.1 generated_examples/baremetal-nodeselector.yaml from examples/baremetal-nodeselector.yaml
Generating with helm v3.10.1 generated_examples/baremetal-priority-critical.yaml from examples/baremetal-priority-critical.yaml
Generating with helm v3.10.1 generated_examples/baremetal-priority-noncritical.yaml from examples/baremetal-priority-noncritical.yaml
Generating with helm v3.10.1 generated_examples/baremetal-prometheus.yaml from examples/baremetal-prometheus.yaml
Generating with helm v3.10.1 generated_examples/baremetal-provisioner.yaml from examples/baremetal-provisioner.yaml
Generating with helm v3.10.1 generated_examples/baremetal-resyncperiod.yaml from examples/baremetal-resyncperiod.yaml
Generating with helm v3.10.1 generated_examples/baremetal-tolerations.yaml from examples/baremetal-tolerations.yaml
Generating with helm v3.10.1 generated_examples/baremetal-without-rbac.yaml from examples/baremetal-without-rbac.yaml
Generating with helm v3.10.1 generated_examples/baremetal-with-resource-limits.yaml from examples/baremetal-with-resource-limits.yaml
Generating with helm v3.10.1 generated_examples/baremetal.yaml from examples/baremetal.yaml
Generating with helm v3.10.1 generated_examples/development-gce.yaml from examples/development-gce.yaml
Generating with helm v3.10.1 generated_examples/development-gke.yaml from examples/development-gke.yaml
Generating with helm v3.10.1 generated_examples/eks-nvme-ssd.yaml from examples/eks-nvme-ssd.yaml
Generating with helm v3.10.1 generated_examples/gce-retain.yaml from examples/gce-retain.yaml
Generating with helm v3.10.1 generated_examples/gce.yaml from examples/gce.yaml
Generating with helm v3.10.1 generated_examples/gke-nvme-ssd-block-raid.yaml from examples/gke-nvme-ssd-block-raid.yaml
Generating with helm v3.10.1 generated_examples/gke.yaml from examples/gke.yaml
Done.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Release note:

none

[k8s-ci-robot]

Hi @jamesalford. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

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.

[andyzhangx]

/ok-to-test

[andyzhangx]

@jamesalford can you fix the error, you need to make changes in examples/additional-volumes.yaml

==== HELM v3====
Checking examples/additional-volumes.yaml failed, diff: 
attachment
--- generated_examples/additional-volumes.yaml	2024-07-18 06:27:38.970631925 +0000
+++ /tmp/tmp.iFYEKeDvEe	2024-07-18 06:34:24.406931414 +0000
@@ -104,6 +104,7 @@
       annotations:
         checksum/config: 997271ac2c9e49ae617e255f4d6e709709aa662e1049fef537e81f1b4d6b36a9
     spec:
+      hostPID: false
       serviceAccountName: local-static-provisioner
       nodeSelector:
         kubernetes.io/os: linux
make: *** [Makefile:48: verify] Error 1

[andyzhangx]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, jamesalford

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx]

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