v1.19.1 still have AWS ECR authentication problem

[fshiori]

Actual behavior
unexpected status code 401 Unauthorized: Not Authorized

Expected behavior
Push image okay.

To Reproduce
Steps to reproduce the behavior:

Additional Information

   image:
     name: gcr.io/kaniko-project/executor:v1.19.1-debug
     entrypoint: [""]
   cache: {}
   before_script: []
   script:
     - mkdir -p /kaniko/.docker
     - echo "{\"credsStore\":\"ecr-login\"}" > /kaniko/.docker/config.json
     - /kaniko/executor --snapshot-mode=time --single-snapshot --use-new-run --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/build/Dockerfile --destination $CI_REGISTRY_IMAGE/$COMPONENT:$CI_COMMIT_SHORT_SHA --destination $CI_REGISTRY_IMAGE/$COMPONENT:latest --destination $CI_REGISTRY_IMAGE/$COMPONENT:$CI_COMMIT_BRANCH-$CI_COMMIT_SHORT_SHA

Triage Notes for the Maintainers

Description	Yes/No
Please check if this a new feature you are proposing	- [ No ]
Please check if the build works in docker but not in kaniko	- [ Yes ]
Please check if this error is seen when you use --cache flag	- [ No ]
Please check if your dockerfile is a multistage dockerfile	- [ Yes ]

[tjdett]

IRSA (AWS_WEB_IDENTITY_TOKEN) is definitely broken. I'm not sure about whether a simpler auth method like IAM User environment variable credentials still works.

[aaron-prindle]

Thanks for flagging this, kaniko has rolled back latest, debug and slim tags to v1.18.0. Closing this issue as dupe, there is another tracking bug here - #2882