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
We have an issue when traffic from the nginx ingress controller to our applications does not have mTLS in our AKS cluster.
Our linkerd setup is with annotations: nginx.ingress.kubernetes.io/service-upstream: "true" with controller: podAnnotations: linkerd.io/inject: enabled, helm stable-2.12.0.
Any help or suggestions on how to debug this issue is much appreciated.
Traffix is secured between prometheus and application, but not between ingress-controller and application.
❯ linkerd viz edges po -n team-platform
SRC DST SRC_NS DST_NS SECURED
prometheus-58f576946-5szhg platform-test-api-68fbcdfdc9-84cp9 linkerd-viz team-platform √
prometheus-58f576946-5szhg platform-test-api-68fbcdfdc9-ltzkh linkerd-viz team-platform √
platform-test-api-68fbcdfdc9-84cp9 splunk-otel-collector-agent-bnfcq team-platform system-monitoring Not Provided By Service Discovery
platform-test-api-68fbcdfdc9-ltzkh splunk-otel-collector-agent-ptbkr team-platform system-monitoring Not Provided By Service Discovery
When calling endpoint getting such response from linkerd tap
❯ linkerd check
Linkerd core checks
===================
kubernetes-api
--------------
√ can initialize the client
√ can query the Kubernetes API
kubernetes-version
------------------
√ is running the minimum Kubernetes API version
√ is running the minimum kubectl version
linkerd-existence
-----------------
√ 'linkerd-config' config map exists
√ heartbeat ServiceAccount exist
√ control plane replica sets are ready
√ no unschedulable pods
√ control plane pods are ready
√ cluster networks contains all pods
linkerd-config
--------------
√ control plane Namespace exists
√ control plane ClusterRoles exist
√ control plane ClusterRoleBindings exist
√ control plane ServiceAccounts exist
√ control plane CustomResourceDefinitions exist
√ control plane MutatingWebhookConfigurations exist
√ control plane ValidatingWebhookConfigurations exist
√ proxy-init container runs as root user if docker container runtime is used
linkerd-cni-plugin
------------------
√ cni plugin ConfigMap exists
√ cni plugin ClusterRole exists
√ cni plugin ClusterRoleBinding exists
√ cni plugin ServiceAccount exists
√ cni plugin DaemonSet exists
√ cni plugin pod is running on all nodes
linkerd-identity
----------------
√ certificate config is valid
√ trust anchors are using supported crypto algorithm
√ trust anchors are within their validity period
√ trust anchors are valid for at least 60 days
√ issuer cert is using supported crypto algorithm
√ issuer cert is within its validity period
‼ issuer cert is valid for at least 60 days
issuer certificate will expire on 2022-09-29T06:57:33Z
see https://linkerd.io/2.12/checks/#l5d-identity-issuer-cert-not-expiring-soon for hints
√ issuer cert is issued by the trust anchor
linkerd-webhooks-and-apisvc-tls
-------------------------------
√ proxy-injector webhook has valid cert
‼ proxy-injector cert is valid for at least 60 days
certificate will expire on 2022-09-28T06:57:33Z
see https://linkerd.io/2.12/checks/#l5d-proxy-injector-webhook-cert-not-expiring-soon for hints
√ sp-validator webhook has valid cert
‼ sp-validator cert is valid for at least 60 days
certificate will expire on 2022-09-28T06:57:34Z
see https://linkerd.io/2.12/checks/#l5d-sp-validator-webhook-cert-not-expiring-soon for hints
√ policy-validator webhook has valid cert
‼ policy-validator cert is valid for at least 60 days
certificate will expire on 2022-09-28T06:57:34Z
see https://linkerd.io/2.12/checks/#l5d-policy-validator-webhook-cert-not-expiring-soon for hints
linkerd-version
---------------
√ can determine the latest version
‼ cli is up-to-date
is running version 2.12.0 but the latest stable version is 2.12.1
see https://linkerd.io/2.12/checks/#l5d-version-cli for hints
control-plane-version
---------------------
√ can retrieve the control plane version
‼ control plane is up-to-date
is running version 2.12.0 but the latest stable version is 2.12.1
see https://linkerd.io/2.12/checks/#l5d-version-control for hints
√ control plane and cli versions match
linkerd-control-plane-proxy
---------------------------
√ control plane proxies are healthy
‼ control plane proxies are up-to-date
some proxies are not running the current version:
* linkerd-destination-69f44dd76c-zczxl (stable-2.12.0)
* linkerd-identity-5c58cd894-mnwv7 (stable-2.12.0)
* linkerd-proxy-injector-566dbb58b8-zftt2 (stable-2.12.0)
see https://linkerd.io/2.12/checks/#l5d-cp-proxy-version for hints
√ control plane proxies and cli versions match
Linkerd extensions checks
=========================
linkerd-smi
-----------
‼ Linkerd extension command linkerd-smi exists
exec: "linkerd-smi": executable file not found in $PATH
see https://linkerd.io/2.12/checks/#extensions for hints
linkerd-viz
-----------
√ linkerd-viz Namespace exists
√ linkerd-viz ClusterRoles exist
√ linkerd-viz ClusterRoleBindings exist
√ tap API server has valid cert
‼ tap API server cert is valid for at least 60 days
certificate will expire on 2022-09-28T03:04:23Z
see https://linkerd.io/2.12/checks/#l5d-tap-cert-not-expiring-soon for hints
√ tap API service is running
√ linkerd-viz pods are injected
√ viz extension pods are running
√ viz extension proxies are healthy
‼ viz extension proxies are up-to-date
some proxies are not running the current version:
* metrics-api-67c8dbb95d-n56fj (stable-2.12.0)
* prometheus-58f576946-5szhg (stable-2.12.0)
* tap-9c95cc4dd-8b6nz (stable-2.12.0)
* tap-injector-54c9cfb879-5bs4v (stable-2.12.0)
* web-76ffcf8447-6sklt (stable-2.12.0)
see https://linkerd.io/2.12/checks/#l5d-viz-proxy-cp-version for hints
√ viz extension proxies and cli versions match
√ prometheus is installed and configured correctly
√ can initialize the client
√ viz extension self-check
Status check results are √
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have an issue when traffic from the nginx ingress controller to our applications does not have mTLS in our AKS cluster.
Our linkerd setup is with
annotations: nginx.ingress.kubernetes.io/service-upstream: "true"
withcontroller: podAnnotations: linkerd.io/inject: enabled
, helm stable-2.12.0.Any help or suggestions on how to debug this issue is much appreciated.
Traffix is secured between prometheus and application, but not between ingress-controller and application.
When calling endpoint getting such response from linkerd tap
and also logs from
linkerd-proxy
on ingress-conroller during a call to the appBeta Was this translation helpful? Give feedback.
All reactions