-
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
Open
mmurph3
wants to merge
8
commits into
main
Choose a base branch
from
severity-defs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Severity defs #1104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chipzoller
requested changes
Jul 30, 2024
@mmurph3, can you resolve conflicts? |
@mmurph3, final bump. |
fix conflict
fix conflict
remove copy reports script. No longer exists.
thomasvn
reviewed
Sep 20, 2024
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. |
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?
thomasvn
reviewed
Sep 20, 2024
@@ -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. |
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.
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. |
Conflicts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue
Proposed Changes