Skip to content

Annotations for setting debug image and debug image version not taking effect #13636

@fragglehunter

Description

@fragglehunter

What is the issue?

When setting the annotations config.linkerd.io/debug-image and config.linkerd.io/debug-image-version on a workload, the debug container never reflects the specified image or version in the annotation.

How can it be reproduced?

Yes, by setting the following annotation on a workload:

        config.linkerd.io/debug-image: cr.l5d.io/linkerd/debug
        config.linkerd.io/debug-image-version: edge-24.2.4
        config.linkerd.io/enable-debug-sidecar: "true"

Logs, error output, etc

The following logs are from proxy-injector, but didnt have any errors:

time="2025-02-06T20:51:26Z" level=info msg="received admission review request \"53b9b137-dae8-42c6-9687-b282e97a570d\""
time="2025-02-06T20:51:26Z" level=info msg="received pod/face-6fb8db9f7f-"
time="2025-02-06T20:51:26Z" level=info msg="inject debug container"
time="2025-02-06T20:51:26Z" level=info msg="injection patch generated for: pod/face-6fb8db9f7f-"

output of linkerd check -o short

linkerd-version
---------------
‼ cli is up-to-date
    is running version 2.15.7 but the latest enterprise version is 2.17.1
    see https://linkerd.io/2/checks/#l5d-version-cli for hints

control-plane-version
---------------------
‼ control plane is up-to-date
    is running version 2.17.0-0 but the latest enterprise version is 2.17.1-0
    see https://linkerd.io/2/checks/#l5d-version-control for hints
‼ control plane and cli versions match
    control plane running enterprise-2.17.0-0-fips but cli running enterprise-2.15.7
    see https://linkerd.io/2/checks/#l5d-version-control for hints

linkerd-control-plane-proxy
---------------------------
‼ control plane proxies are up-to-date
    some proxies are not running the current version:
        * linkerd-destination-584c89ff-hx5dt (enterprise-2.17.0-0-fips)
        * linkerd-enterprise-748c6c8fcb-v4d2s (enterprise-2.17.0-0-fips)
        * linkerd-identity-78cf7778d4-2mpmw (enterprise-2.17.0-0-fips)
        * linkerd-proxy-injector-6484648bc4-6tcqg (enterprise-2.17.0-0-fips)
    see https://linkerd.io/2/checks/#l5d-cp-proxy-version for hints
‼ control plane proxies and cli versions match
    linkerd-destination-584c89ff-hx5dt running enterprise-2.17.0-0-fips but cli running enterprise-2.15.7
    see https://linkerd.io/2/checks/#l5d-cp-proxy-cli-version for hints

linkerd-buoyant
---------------
‼ linkerd-buoyant cli is up-to-date
    CLI version is v0.33.3 but the latest is v0.33.4
    see https://docs.buoyant.io/buoyant-enterprise-linkerd/latest/tasks/troubleshooting/#cli-up-to-date for hints
‼ linkerd-control-plane-operator Deployment is up-to-date
    incorrect app.kubernetes.io/version label: v0.33.2, expected: v0.33.4
    see https://docs.buoyant.io/buoyant-enterprise-linkerd/latest/tasks/troubleshooting/#linkerd-control-plane-operator-up-to-date for hints
‼ linkerd-control-plane-validator Deployment is up-to-date
    incorrect app.kubernetes.io/version label: v0.33.2, expected: v0.33.4
    see https://docs.buoyant.io/buoyant-enterprise-linkerd/latest/tasks/troubleshooting/#linkerd-control-plane-validator-up-to-date for hints
‼ linkerd-data-plane-operator Deployment is up-to-date
    incorrect app.kubernetes.io/version label: v0.33.2, expected: v0.33.4
    see https://docs.buoyant.io/buoyant-enterprise-linkerd/latest/tasks/troubleshooting/#linkerd-data-plane-operator-up-to-date for hints

Status check results are √

Environment

  • Kubernetes Version: v1.30.3
  • Cluster Environment: On-Prem Cluster
  • Host OS: Ubuntu 22.04.4 LTS
  • Linkerd Version: 2.17.1

Possible solution

No response

Additional context

No response

Would you like to work on fixing this bug?

None

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions