You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The manager currently detects at runtime if istio is available or not and then decides to manage some istio resources. The typical istio annotations are present independent of if istio is detected or not.
There can be situations where users want to use istio but run the telemetry module in non-istio mode. For that, a new module config setting is required to explicitly disable the istio mode. Also it must be assured that really any Istio feature is disabled.
Criterias
As a user I can explicitly disable the istio mode
Having the istio mode disabled, a running istio installation has no impact to the telemetry setup (no istio annotations are getting configured, no istio resources are generated)
Istio input of MetricPipelineis still supported, people only want to disable running telemetry with istio
Prometheus input of MetricPipeline does not support scraping from mtls endpoint
Reasons
Attachments
Release Notes
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.
Description
The manager currently detects at runtime if istio is available or not and then decides to manage some istio resources. The typical istio annotations are present independent of if istio is detected or not.
There can be situations where users want to use istio but run the telemetry module in non-istio mode. For that, a new module config setting is required to explicitly disable the istio mode. Also it must be assured that really any Istio feature is disabled.
Criterias
Reasons
Attachments
Release Notes
The text was updated successfully, but these errors were encountered: