-
Notifications
You must be signed in to change notification settings - Fork 211
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
single pod deployments #282
single pod deployments #282
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pohly 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:
Approvers can indicate their approval by writing |
kubernetes-csi/csi-driver-host-path#282 introduces two kinds of deployments, with one pod for sidecar and driver (now the default) individual pods for sidecars and drivers (what used to be the default, now in a "-prow" flavor for testing with Prow). We want to test both flavors before merging and periodically.
/test pull-kubernetes-csi-csi-driver-host-path-1-21-on-kubernetes-1-21 |
12d9b6e
to
b813602
Compare
kubernetes-csi/csi-driver-host-path#282 introduces two kinds of deployments, with one pod for sidecar and driver (now the default) and individual pods for sidecars and drivers (what used to be the default, now in a "-prow" flavor for testing with Prow). We want to test both flavors before merging and periodically.
kubernetes-csi/csi-driver-host-path#282 introduces two kinds of deployments, with one pod for sidecar and driver (now the default) and individual pods for sidecars and drivers (what used to be the default, now in a "-prow" flavor for testing with Prow). We want to test both flavors before merging and periodically.
kubernetes-csi/csi-driver-host-path#282 introduces two kinds of deployments, with one pod for sidecar and driver (now the default) and individual pods for sidecars and drivers (what used to be the default, now in a "-prow" flavor for testing with Prow). We want to test both flavors before merging and periodically.
kubernetes-csi/csi-driver-host-path#282 introduces two kinds of deployments, with one pod for sidecar and driver (now the default) and individual pods for sidecars and drivers (what used to be the default, now in a "-test" flavor for testing with Prow). We want to test both flavors before merging and periodically.
/retest |
b2bdc34
to
43c5d7e
Compare
All deployments are greater than 1.16, therefore we can deploy csi-hostpath-snapshotclass.yaml unconditionally.
The kubernetes-x.yy deployments now use the same pod for driver and sidecars, which is the usual way of deploying them. The alternative "-prow" deployments use separate pods for them to test that the individual RBAC rules are correct.
43c5d7e
to
194132f
Compare
/retest Test flake (?) in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-csi_csi-driver-host-path/282/pull-kubernetes-csi-csi-driver-host-path-1-21-test-on-kubernetes-1-21/1389899497311571968: "External Storage [Driver: hostpath.csi.k8s.io] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource" |
/lgtm |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
We want to show (and, in Kubernetes, test) deployments with all sidecars and driver in the same pod. We still want to test with individual pods to ensure that RBAC rules work, therefore we need both flavors.
Which issue(s) this PR fixes:
Fixes #192
Special notes for your reviewer:
Based on PR #281
Depends on an updated prow.sh and new Prow jobs for the non-default deployments.
Does this PR introduce a user-facing change?: