-
Notifications
You must be signed in to change notification settings - Fork 0
S3CSI-204: Support CA certificates via ConfigMap #351
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
Changes from 4 commits
8c0450d
2c0b663
5ae289d
164fdb1
f0fbf68
26352e4
063ad0a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -153,6 +153,25 @@ value: {{ coalesce .Values.node.s3EndpointUrl .Values.s3.endpointUrl | quote }} | |
| | `mountpointPod.headroomImage.tag` | Image tag for headroom pods. | `3.10` | No | | ||
| | `mountpointPod.headroomImage.pullPolicy` | Image pull policy for headroom pods. | `IfNotPresent` | No | | ||
|
|
||
| ## TLS Configuration | ||
|
|
||
| <!-- markdownlint-disable MD046 --> | ||
|
||
| !!! info "Custom CA Certificates" | ||
| When your S3 endpoint uses TLS with a private or internal CA, configure the `tls.*` parameters to inject the CA certificate. | ||
| The ConfigMap must exist in **two** namespaces (controller and mounter pod) because they run in separate namespaces. | ||
| See the [TLS Configuration Guide](../driver-deployment/tls-configuration.md) for ordering constraints and setup instructions. | ||
| <!-- markdownlint-enable MD046 --> | ||
|
|
||
| | Parameter | Description | Default | Required | | ||
| |------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-----------------------------| | ||
| | `tls.caCertConfigMap` | Name of the ConfigMap containing the CA certificate bundle (key: `ca-bundle.crt`). Must exist in both the controller namespace and `mountpointPod.namespace`. Create in the controller namespace **before** Helm install, and in `mountpointPod.namespace` **after** (since Helm creates that namespace). If missing from either namespace, the respective pod stays in `ContainerCreating`. Leave empty to disable. | `""` | No | | ||
| | `tls.initImage.repository` | Image repository for the CA certificate installation initContainer in mounter pods. | `alpine` | No | | ||
| | `tls.initImage.tag` | Image tag for the CA certificate installation initContainer. | `3.21` | No | | ||
| | `tls.initImage.pullPolicy` | Pull policy for the CA certificate init image. | `IfNotPresent` | No | | ||
| | `tls.initResources.requests.cpu` | CPU request for the CA certificate init container. | `10m` | No | | ||
| | `tls.initResources.requests.memory` | Memory request for the CA certificate init container. | `16Mi` | No | | ||
| | `tls.initResources.limits.memory` | Memory limit for the CA certificate init container. | `64Mi` | No | | ||
|
|
||
| ## CRD Cleanup Configuration (v2.0) | ||
|
|
||
| | Parameter | Description | Default | Required | | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The JUnit report is written to
./test-results/e2e-tls-tests-results.xmlviaJUNIT_REPORT, but the Codecov upload step points to./tests/e2e/test-results/e2e-tls-tests-results.xml. This mismatch will cause the Codecov step to fail to find the report (or upload an empty/missing file). Align the paths (either write into./tests/e2e/test-results/or upload from./test-results/).