pulp
There is no way to pass CA when S3 https enables
Version 1.0.0
Describe the bug STORAGES = { "default": { "BACKEND": "storages.backends.s3boto3.S3Boto3Storage", "OPTIONS": { "signature_version": "s3v4", "addressing_style": "path", "bucket_name": 'test', "secret_key": "<secret_key>", "access_key": "<access_key>", "endpoint_url": "https://example.com", }, }, "staticfiles": {"BACKEND": "django.contrib.staticfiles.storage.StaticFilesStorage"}, } 'm trying to set up a custom connection to s3 as a backend. s3 works exclusively via https and a self-signed certificate. It turns out that you either need to ignore ssl (for example, in docker-compose this is done using "verify": False) or add a custom CA to the pod with the application. There is a setting for the mount_trusted_ca operator, but it is only for openshift To Reproduce Install chart and try to configure it with custom s3 on self-signed certificate not in openshift
Expected behavior There should be a documented way to set up such a connection. Additional context Add any other context about the problem here. Please provide links to any previous discussions via Discourse or Bugzilla.
