kubectl logs label don't work

[0xttfx]

i have a Linkerd functional installation, but i have a problem or my ignorance does not allow me to understand the "problem"

Version and Check:

$ linkerd version
Client version: stable-2.12.1
Server version: stable-2.12.1`

$ 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-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 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
√ sp-validator webhook has valid cert
√ sp-validator cert is valid for at least 60 days
√ policy-validator webhook has valid cert
√ policy-validator cert is valid for at least 60 days
linkerd-version
√ can determine the latest version
√ cli is up-to-date
control-plane-version
√ can retrieve the control plane version
√ control plane is up-to-date
√ control plane and cli versions match
linkerd-control-plane-proxy
√ control plane proxies are healthy
√ control plane proxies are up-to-date
√ control plane proxies and cli versions match
linkerd-ha-checks
√ pod injection disabled on kube-system
Linkerd extensions checks
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
√ 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
√ 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 √

Problem

when I try to access the deployment log using the label

$ kubectl logs -f -l 'run=PaymentStreamApp' --namespace prod 
Defaulted container "linkerd-proxy" out of: linkerd-proxy, payment-stream, linkerd-init (init)
[     0.002458s]  INFO ThreadId(01) linkerd2_proxy::rt: Using single-threaded proxy runtime
[     0.003085s]  INFO ThreadId(01) linkerd2_proxy: Admin interface on 0.0.0.0:4191
[     0.003095s]  INFO ThreadId(01) linkerd2_proxy: Inbound interface on 0.0.0.0:4143
[     0.003096s]  INFO ThreadId(01) linkerd2_proxy: Outbound interface on 127.0.0.1:4140
[     0.003098s]  INFO ThreadId(01) linkerd2_proxy: Tap interface on 0.0.0.0:4190
[     0.003100s]  INFO ThreadId(01) linkerd2_proxy: Local identity is default.prod.serviceaccount.identity.linkerd.cluster.local
[     0.003102s]  INFO ThreadId(01) linkerd2_proxy: Identity verified via linkerd-identity-headless.linkerd.svc.cluster.local:8080 (linkerd-identity.linkerd.serviceaccount.identity.linkerd.cluster.local)
[     0.003104s]  INFO ThreadId(01) linkerd2_proxy: Destinations resolved via linkerd-dst-headless.linkerd.svc.cluster.local:8086 (linkerd-destination.linkerd.serviceaccount.identity.linkerd.cluster.local)
[     0.033585s]  INFO ThreadId(02) daemon:identity: linkerd_app: Certified identity id=default.prod.serviceaccount.identity.linkerd.cluster.local

I can only access the application log, if I access the container log

$ kubectl logs -n prod --tail=10 -f payment-stream-584723 payment-stream
[./main.js-1] finished ok  undefined
[pg-dispatcher-producer] found new notification "MjI6MTM........="
[pg-dispatcher-producer] received key 
[pg-dispatcher-consumer] start processing key 
[worker-0] Got payload: {"action" : "process_payment", "id" : ".......", "subscription_id" : ".......", "created_at" : "2022-...-....2", "sent_to_queue_at" : "......."}.
[worker-0] Command succeded with status code 0.
...
...

[alpeb]

The label selector -l allows you to select the pod. If you don't specify the container in that pod, kubectl logs will output the logs for the first container, which will always be linkerd's proxy. Does this answer your question? :-)

[0xttfx]

my understanding is that it would bring the log of the linker and application containers...

[0xttfx]

but nothing like RTFM!!!
Thanks @alpeb