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

Severity defs #1104

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Severity defs #1104

wants to merge 8 commits into from

Conversation

mmurph3
Copy link
Contributor

@mmurph3 mmurph3 commented Jul 30, 2024

Related Issue

Proposed Changes

@mmurph3 mmurph3 requested a review from a team as a code owner July 30, 2024 19:58
troubleshooting/kubcost-severity-definitions.md Outdated Show resolved Hide resolved
troubleshooting/kubcost-severity-definitions.md Outdated Show resolved Hide resolved
@chipzoller
Copy link
Contributor

@mmurph3, can you resolve conflicts?

@chipzoller
Copy link
Contributor

@mmurph3, final bump.

@mmurph3 mmurph3 requested a review from chipzoller September 20, 2024 17:16
Comment on lines -297 to -305
### 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.
Copy link
Member

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 [email protected] 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Opening a support case at [email protected] 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 [email protected] 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.

@chipzoller
Copy link
Contributor

Conflicts

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

Successfully merging this pull request may close these issues.

3 participants