Open bmnave opened 3 years ago
@vincent99 and @brandond tried to help me out in the Rancher Slack channel. Step two would seem to indicate creating a secret via the Rancher Cluster Manager UI. Step 3 is actually referencing the chart deployment inside of the Cluster Explorer UI. After following the breadcrumbs they gave me, I'm still unable to set up a Notifier that doesn't fail with x509: certificate signed by unknown authority
.
It would really help if you could provide an example. It feels like I'm experiencing much of the same problems in https://github.com/rancher/rancher/issues/24272
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 90 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 30 days. Thank you for your contributions.
Request Summary: In this section: Trusted CA for Notifiers
The instructions state "Add your trusted CA secret to the
cattle-monitoring-system
namespace" but it doesn't specify the Secret Name and the Secret Key that the Notifier is looking for.Details: n/a