[comment]: # (Note that your PR title should follow the conventional
commit format: https://conventionalcommits.org/en/v1.0.0/#summary)
# PR Description
This removes angular controls in all our dashboards -
12 dashboards - Kubernetes mixin
2 dashboards - node mixin
Total = 14 dashboards.
Please see wiki on guidance for how to update these in the future -
https://msazure.visualstudio.com/DefaultCollection/InfrastructureInsights/_git/InfrastructureInsights.wiki?path=%2FManagedPrometheus%2FPRD%2FGrafanaDashboards%2FGrafana%20Dashboards%20-%20%20Guidance&version=GBwikiMaster
You can see these dashboards in action in below (use
datasource=vishwa-dev-1)--
https://vishwa-dev-backdoor-1-bqdhhmchb3ccffcc.eus.grafana.azure.com/dashboards/f/bdvx50zr829dsd/
(for k8s dashboards including windows)
https://vishwa-dev-backdoor-1-bqdhhmchb3ccffcc.eus.grafana.azure.com/dashboards/f/e5050f06-2b5e-43ca-b7bb-fb900512742d/
(for node dashboards)
Once this gets merged, we will create a PR in Grafana , which will start
upgrading all existing dashboards...
[comment]: # (The below checklist is for PRs adding new features. If a
box is not checked, add a reason why it's not needed.)
# New Feature Checklist
- [ ] List telemetry added about the feature.
- [ ] Link to the one-pager about the feature.
- [ ] List any tasks necessary for release (3P docs, AKS RP chart
changes, etc.) after merging the PR.
- [ ] Attach results of scale and perf testing.
[comment]: # (The below checklist is for code changes. Not all boxes
necessarily need to be checked. Build, doc, and template changes do not
need to fill out the checklist.)
# Tests Checklist
- [ ] Have end-to-end Ginkgo tests been run on your cluster and passed?
To bootstrap your cluster to run the tests, follow [these
instructions](/otelcollector/test/README.md#bootstrap-a-dev-cluster-to-run-ginkgo-tests).
- Labels used when running the tests on your cluster:
- [ ] `operator`
- [ ] `windows`
- [ ] `arm64`
- [ ] `arc-extension`
- [ ] `fips`
- [ ] Have new tests been added? For features, have tests been added for
this feature? For fixes, is there a test that could have caught this
issue and could validate that the fix works?
- [ ] Is a new scrape job needed?
- [ ] The scrape job was added to the folder
[test-cluster-yamls](/otelcollector/test/test-cluster-yamls/) in the
correct configmap or as a CR.
- [ ] Was a new test label added?
- [ ] A string constant for the label was added to
[constants.go](/otelcollector/test/utils/constants.go).
- [ ] The label and description was added to the [test
README](/otelcollector/test/README.md).
- [ ] The label was added to this [PR
checklist](/.github/pull_request_template).
- [ ] The label was added as needed to
[testkube-test-crs.yaml](/otelcollector/test/testkube/testkube-test-crs.yaml).
- [ ] Are additional API server permissions needed for the new tests?
- [ ] These permissions have been added to
[api-server-permissions.yaml](/otelcollector/test/testkube/api-server-permissions.yaml).
- [ ] Was a new test suite (a new folder under `/tests`) added?
- [ ] The new test suite is included in
[testkube-test-crs.yaml](/otelcollector/test/testkube/testkube-test-crs.yaml).
2d57f490b4