-
Notifications
You must be signed in to change notification settings - Fork 94
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump versions to 1.6.10 and 2.0.0-rc.5
Signed-off-by: Pete Wall <pete.wall@grafana.com>
- Loading branch information
Showing
73 changed files
with
330 additions
and
330 deletions.
There are no files selected for viewing
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
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
18 changes: 9 additions & 9 deletions
18
charts/k8s-monitoring-v1/docs/examples/alloy-autoscaling-and-storage/output.yaml
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
18 changes: 9 additions & 9 deletions
18
charts/k8s-monitoring-v1/docs/examples/application-observability/output.yaml
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
18 changes: 9 additions & 9 deletions
18
charts/k8s-monitoring-v1/docs/examples/azure-aks/output.yaml
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
18 changes: 9 additions & 9 deletions
18
charts/k8s-monitoring-v1/docs/examples/bearer-token-auth/output.yaml
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
aa765dd
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.
@petewall [CRITICAL_RISK] Hi, we noticed you made a commit in GitHub that may contain sensitive information (details below). Please double check if you intended to include or share this sensitive information in the issue.
Note that it may have already been addressed automatically by an administrator.
What types of sensitive information were detected?
API Key: Google API
What was the context?
When did this happen?
Wed, 20 Nov 2024 at 16:31:37 UTC
Where did this happen?
Repository: k8s-monitoring-helm
File Path: charts/k8s-monitoring-v1/docs/examples/sigv4-auth/output.yaml