-
Notifications
You must be signed in to change notification settings - Fork 106
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
Severity defs #1104
base: main
Are you sure you want to change the base?
Severity defs #1104
Conversation
@mmurph3, can you resolve conflicts? |
@mmurph3, final bump. |
fix conflict
fix conflict
remove copy reports script. No longer exists.
### Saved reports not appearing in Kubecost UI after upgrading to v2 | ||
|
||
After upgrading Kubecost to v2, saved reports may not properly display in the Kubecost UI. To properly transfer over saved reports, download this [`copy-reports.sh` file](https://github.com/kubecost/kubecost-utilities/blob/main/copy-reports/copy-reports.sh), then run the following command: | ||
|
||
``` | ||
bash copy-reports.sh | ||
``` | ||
|
||
Saved reports should then populate in your upgraded Kubecost version. |
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.
@mmurph3 Based on your observations, this is no longer an issue?
@@ -0,0 +1,12 @@ | |||
# Kubecost Severity Level Definitions | |||
|
|||
Opening a support case at support@kubecost.com or starting a thread in slack in your private slack channel (Enterprise customers only) can make it easier to share technical data, error messages, and system information with the Kubecost team. |
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.
Opening a support case at support@kubecost.com or starting a thread in slack in your private slack channel (Enterprise customers only) can make it easier to share technical data, error messages, and system information with the Kubecost team. | |
Opening a support case at support@kubecost.com or starting a thread in slack in your private slack channel (Enterprise customers only) can make it easier to share technical data, error messages, and system information with the Kubecost team. |
Conflicts |
Do we want to finalize the changes here? Or is this doc going to be moot with M&A work? |
Related Issue
Proposed Changes