Skip to content
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

s3: Added option to skip tls verify #11050

Closed
wants to merge 10 commits into from

Conversation

Sheikh-Abubaker
Copy link
Contributor

@Sheikh-Abubaker Sheikh-Abubaker commented Oct 26, 2023

What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #10030

Special notes for your reviewer:

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • CHANGELOG.md updated
    • If the change is worth mentioning in the release notes, add add-to-release-notes label
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md. Example PR
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory.

@david-nano
Copy link

I don't see any change on the templates of the helm chart. How do the implementation will be applied?

@Sheikh-Abubaker
Copy link
Contributor Author

I don't see any change on the templates of the helm chart. How do the implementation will be applied?

I went through the official documentation : https://grafana.com/docs/loki/latest/configure/#s3_storage_config

Here there is a parameter defined insecure_skip_verify which states that enabling the mentioned parameter will
help to skip verification of certificate.

image

Signed-off-by: Sheikh-Abubaker <[email protected]>
@Sheikh-Abubaker
Copy link
Contributor Author

Hi @david-nano, is this PR up to the mark for resolving the respective issue ?

@j4rj4r
Copy link
Contributor

j4rj4r commented Oct 30, 2023

Hello,

This variable must be added by the user only if he needs it. Why put it by default in values.yaml and make it even more complex?

The option already exists, the user just needs to modify the values.yaml and run helm install. No need for a PR.

@david-nano
Copy link

respective

Yes it is

@Sheikh-Abubaker
Copy link
Contributor Author

Sheikh-Abubaker commented Jan 6, 2024

@JStickler can you please request review for this PR it's been a while since I've opened this PR, if there are any changes needed I'd be glad to contribute.

@Sheikh-Abubaker
Copy link
Contributor Author

@MichelHollands seems like folks are in need of this feature please see comments of issue #10030

Signed-off-by: Sheikh-Abubaker <[email protected]>
@MichelHollands
Copy link
Contributor

@Sheikh-Abubaker This is not needed. You should specify the insecure_skip_verify setting in the http_config block in the values.yaml you pass when deploying the chart. The change you are making here is changing it in the default values. This will make everyone's installation less secure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Skip tls verify for S3 bucket option on helm chart
4 participants