CrowdStrike / CrowdStrike/falcon-operator

[Feature Request] Falcon Image Analyzer - Add support of Azure Workload Identity

Open
#682 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
79
Forks
51
Avg merge
6h 46m
Merged PRs (30d)
10

Description

Falcon FalconImageAnalyzer not supported Azure Workload Identity ?

Operator CRD documentation mention only "AWS & GCP".

              serviceAccount:
                    description: Define annotations that will be passed down to
                      Image Analyzer service account. This is useful for passing
                      along AWS IAM Role or GCP Workload Identity.

Secondly, crd not allow to patch pod labels required by Azure Workload identity => "azure.workload.identity/use: 'true'"

I patch it manually, but seem not supported as I still face to this error =>

unable to retrieve auth token: invalid username/password: unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information

Although all expected variables was correctly injected on the image analyser pod by the azure workload identity=>

AZURE_TENANT_ID=<....>
AZURE_FEDERATED_TOKEN_FILE=/var/run/secrets/azure/tokens/azure-identity-token
AZURE_AUTHORITY_HOST=https://login.microsoftonline.com/
AZURE_CLIENT_ID=<....>

Azure Workload Identity doc => https://learn.microsoft.com/en-us/azure/aks/workload-identity-overview?tabs=dotnet

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Operator CRD documentation and the Falcon Image Analyzer service account and pod configuration described in the issue. Check how service account annotations and pod labels are exposed, then reproduce the Azure Workload Identity setup and ACR authentication error. Done means Azure annotations and the azure.workload.identity/use label can be configured and the analyzer authenticates successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go, kubernetes
Domain
authentication, cloud, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.