Fix all infos & warnings from istioctl analyze command

[strekm]

Description

Clear out an output of istioctl analyze -n kyma-system and istioctl analyze -n kyma-integration commands. At this moment there are bunch of infos about wrongly named ports and few warnings related to annotations.
kyma-integration.txt
kyma-system.txt

Reasons

Improve visibility of istio related issues, improve troubleshooting & debugging

Attachments
kyma-integration.txt
kyma-system.txt

[ghost]

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.

[mjakobczyk]

It seems that some of the port names connected with Tracing can not be changed on Kyma side as they are defined in jaeger-operator itself.
As a result, following infos would not be addressed:

Info [IST0118] (Service tracing-jaeger-agent.kyma-system) Port name config-rest (port: 5778, targetPort: 5778) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service tracing-jaeger-collector-headless.kyma-system) Port name c-tchan-trft (port: 14267, targetPort: 14267) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service tracing-jaeger-collector.kyma-system) Port name c-tchan-trft (port: 14267, targetPort: 14267) doesn't follow the naming convention of Istio port.

[cnvergence]

For the duplicate certificate in the application-connector gateway, we won't push any changes

Warning [IST0138] (Gateway kyma-system/kyma-gateway-application-connector) Duplicate certificate in multiple gateways [kyma-system/kyma-gateway-application-connector kyma-system/kyma-gateway] may cause 404s if clients re-use HTTP2 connections.

Please see the explanation here

[cnvergence]

The same goes for the annotations in jaeger controlled by tracing-operator

Warning [IST0107] (Deployment kyma-system/tracing-jaeger) Misplaced annotation: sidecar.istio.io/inject can only be applied to Pod
Warning [IST0107] (Deployment kyma-system/tracing-jaeger) Misplaced annotation: sidecar.istio.io/rewriteAppHTTPProbers can only be applied to Pod

Currently it is not possible to properly set those annotations

[cnvergence]

I have opened the issue in the jaeger-operator helm chart

• Unable to set sidecar.istio.io Pod annotations in jaeger pod jaegertracing/helm-charts#355

[cnvergence]

Port change can also be tracked here

• Add http- prefix to port names in collector and agent services jaegertracing/jaeger-operator#1862

[cnvergence]

PRs to jaeger-operator were merged and released with 1.34.0, but we are blocked by this issue in the helm chart

• jagger-operator 1.32.0 fails to start successfully jaegertracing/helm-charts#351

[cnvergence]

Helm charts of jaeger-operator were fixed

• jagger-operator 1.32.0 fails to start successfully jaegertracing/helm-charts#351 (comment)

This issue can be closed after bumping jaeger-operator to 1.34.0 version

[github-actions]

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.

[github-actions]

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.

[johgoe]

Warning [IST0107] (Deployment kyma-system/tracing-jaeger) Misplaced annotation: sidecar.istio.io/inject can only be applied to Pod
Warning [IST0107] (Deployment kyma-system/tracing-jaeger) Misplaced annotation: sidecar.istio.io/rewriteAppHTTPProbers can only be applied to Pod
Info [IST0118] (Service kyma-system/monitoring-kube-state-metrics) Port name metrics (port: 8081, targetPort: 8081) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service kyma-system/telemetry-operator-webhook) Port name  (port: 443, targetPort: 9443) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service kyma-system/tracing-jaeger-collector-headless) Port name otlp-grpc (port: 4317, targetPort: 4317) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service kyma-system/tracing-jaeger-collector-headless) Port name otlp-http (port: 4318, targetPort: 4318) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service kyma-system/tracing-jaeger-collector) Port name otlp-grpc (port: 4317, targetPort: 4317) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service kyma-system/tracing-jaeger-collector) Port name otlp-http (port: 4318, targetPort: 4318) doesn't follow the naming convention of Istio port.
Info [IST0118] (Service kyma-system/tracing-metrics) Port name cr-metrics (port: 8686, targetPort: 8686) doesn't follow the naming convention of Istio port.
Info [IST0135] (Deployment kyma-system/tracing-jaeger) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/alertmanager-monitoring-alertmanager-0) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/cluster-essentials-pod-preset-webhook-858f8d446f-58mvt) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/cluster-essentials-pod-preset-webhook-858f8d446f-zwpbf) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/eventing-nats-0) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/eventing-nats-1) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/eventing-nats-2) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/kiali-78d5479f95-jgvhm) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/logging-loki-0) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/monitoring-kube-state-metrics-858cd64f74-xp7bb) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/monitoring-operator-5566cf78-wxvn2) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/monitoring-prometheus-istio-server-54cfc5f7b5-5pgst) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/prometheus-monitoring-prometheus-0) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/serverless-ctrl-mngr-657b8cc46-mcrtd) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/serverless-webhook-svc-5c58cd8bcd-vqw2k) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/telemetry-operator-66f4f47ff7-426qq) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.
Info [IST0135] (Pod kyma-system/tracing-jaeger-679ddc6979-n5969) Annotation "sidecar.istio.io/inject" has been deprecated in favor of the "sidecar.istio.io/inject" label and may not work in future Istio versions.

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[kyma-bot]

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

[kyma-bot]

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.