kubecost / features-bugs

A public repository for filing of Kubecost feature requests and bugs. Please read the issue guidelines before filing an issue here.
0 stars 0 forks source link

Not receiving the scheduled report emails #21

Closed renjithtc closed 1 month ago

renjithtc commented 1 year ago

Hello Team,

I recently deployed Kubecost (version v1.106.4) in my Kubernetes cluster and have set up a scheduled report. However, I'm not receiving the scheduled report emails, and I suspect that the sender email ID and relay server details need to be configured.

I would appreciate any guidance on where and how I can configure these details within Kubecost. Specifically, I would like to know:

The email domain used by Kubecost to send scheduled reports. The configuration location for setting the sender email ID. The steps to configure the email/relay server details in Kubecost. Your assistance in resolving this matter is highly valued. Thank you in advance for your help!

Regards, Renjith

AjayTripathy commented 1 year ago

Hi @renjithtc emails come from team@kubecost.com via Sendgrid today. We don't have support for configuring your own sender email ID or your own relay server in the community edition today, though you can contact us at the same address (team@kubecost.com) to learn more about how to set that up.

What receiver email have you provided? I can look to see if that's being bounced.

renjithtc commented 1 year ago

Hi @AjayTripathy appreciate your prompt response!

Considering security constraints, we are currently unable to utilize any external relay server to send emails. Our objective is to schedule the report and send it to the client via email. If configuring an internal relay server isn’t supported in the Kubecost Community Edition, could you kindly explore alternative solutions such as utilizing an API call? Your insights on this matter would be greatly helpful

chipzoller commented 1 year ago

Transferring to features-bugs as this does not appear to be something for the Helm chart.

AjayTripathy commented 1 year ago

@renjithtc you can certainly instrument your own email using the APIs documented here: https://docs.kubecost.com/apis/apis-overview

chipzoller commented 1 month ago

Hello, in an effort to consolidate our bug and feature request tracking, we are deprecating using GitHub to track tickets. If this issue is still outstanding and you have not done so already, please raise a request at https://support.kubecost.com/.