Add control plane Istio scrape config and settings#1393
Merged
rashmichandrashekar merged 16 commits intomainfrom Mar 23, 2026
Merged
Add control plane Istio scrape config and settings#1393rashmichandrashekar merged 16 commits intomainfrom
rashmichandrashekar merged 16 commits intomainfrom
Conversation
6e08df7 to
f9bbe8b
Compare
Contributor
|
@shalier - Could you pls add description of what you are trying to do and what metrics are being scraped with these jobs? |
164446f to
5b49aa2
Compare
Contributor
Contributor
|
This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Contributor
|
This PR was closed because it has been stalled for 12 days with no activity. |
Contributor
Author
|
These are the labels collected -
|
Contributor
|
This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
88ce6ca to
959d0ce
Compare
|
Azure Pipelines successfully started running 1 pipeline(s). |
6fe8935 to
e788ace
Compare
rashmichandrashekar
approved these changes
Mar 19, 2026
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
gracewehner
added a commit
that referenced
this pull request
Mar 20, 2026
Analyzed review comments across PRs #1393, #1397, #1403, #1408, #1452 to extract team conventions and common pitfalls: - ME CLI arg formatting (leading dash) - Keep vs drop list preference for scrape configs - Helm values defaults (features off by default) - CCP vs addon chart parity - Extension migration coordination - Build flag consistency with dalec-build-defs - Test coverage requirements (Ginkgo E2E, TestKube) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
[comment]: # (Note that your PR title should follow the conventional commit format: https://conventionalcommits.org/en/v1.0.0/#summary) [comment]: # (The below checklist is for PRs adding new features. If a box is not checked, add a reason why it's not needed.) This is merging into another feature branch - [ ] 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.) - [ ] 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).
The preceding test steps (e.g. errorprone global ext labels) leave behind ama-metrics-prometheus-config configmaps with invalid config (e.g. scrape_interval as integer instead of string). When the controlplane-istio test runs without cleaning these up, the config merger takes the custom config path, validation fails, and the fallback produces only 10 default scrape configs instead of the expected 11 (10 default + controlplane-istio). Add kubectl delete --ignore-not-found for the three custom prometheus configmaps before applying the controlplane-istio settings configmap.
e788ace to
be01076
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
rashmichandrashekar
approved these changes
Mar 23, 2026
This file contains hidden or 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
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.
PR Description
This PR adds support for scraping Prometheus metrics from Istio Control Plane (MCP - Managed Control Plane) components in AKS clusters with Azure-managed Istio service mesh enabled. Metrics being scraped:
citadel_server_csr_countgalley_validation_failedgalley_validation_passedpilot_conflict_inbound_listenerpilot_conflict_outbound_listener_http_over_current_tcppilot_conflict_outbound_listener_tcp_over_current_httppilot_conflict_outbound_listener_tcp_over_current_tcppilot_infopilot_proxy_convergence_time*_sum,_count,_bucket)pilot_servicespilot_virt_servicespilot_xdspilot_xds_push_context_errorspilot_xds_pushesNew Feature Checklist
Tests Checklist
operatorwindowsarm64arc-extensionfips/tests) added?