Change:
WRT , container registry credentials should be included in a docker file instead. We deprecated for this reason in , but is more tricky, because the file it references is not static. We need to figure out what the alternative is for dynamically providing pull credentials to nodes. /cc
I think we need to enable Managed Service Identity (MSI) for all instances before deprecating . To do this, we also need to grant VM access to Resource Group in Azure IAM (e.g. config Azure AD in acs-engine). WDYT?
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
I think this is still active. Right, /remove-lifecycle stale
Thanks, this is still active
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
-- What's the status of this?
Sorry, no progress yet. Any ideas on this?
-- pinging again on this one.
We're not making any progress yet in this release. Still seeking the possible solutions for non-MSI cases, secret is one option for this. /milestone v1.15 Related and
None one is working on this. Let's move this out of 1.15 /milestone v1.16
thanks. This missed v1.15 feature timeline. LGTM of moving to v1.16.
Hello! I'm the bug triage lead for the 1.16 release cycle and considering this issue is tagged for 1.16, I'd like to check its status. The code freeze is starting on August 29th EOD PST (about 5 days from now) and once the code freeze starts, only release-blocking changes will be considered to be merged. Is this issue still planned to be fixed for the 1.16 release?
/milestone clear is preparing a KEP for this, but it's still not ready yet.
Will follow this KEP for implementation
This should be addressed by /milestone v1.18
Hello ! Bug Triage team here for the 1.18 release. This is a friendly reminder that code freeze is scheduled for 5 March, which is a few weeks from now. Is this issue still intended for 1.18? Thanks in advance!
C/O Code freeze for release 1.18 is starting in 5 March (less than 1 week from now) and we want to ensure that each issue has a chance to be finished on time. Is this still on track for this deadline?
/milestone v1.19 The work on the KEP hasn't started yet, so moving this to 1.19
Hello from Bug Triage team! Wanted to follow up on this issue with a friendly reminder that the code freeze for 1.19 is starting June 25th (about 4 weeks from now). As this issue is tagged for 1.19, is it still planned for this release?
/milestone v1.20
Hey Bug Triage here. Wanted to follow up on the status of this issue as we're approaching code freeze on 12.11.2020. This issue is tagged for 1.20, is it still planned for this release?
Hi Bug Triage here, seeing that there is not much recent activity here, and we are pretty late into code freeze, I am going to remove the milestone label. /milestone clear
/triage accepted /priority backlog I think we would be able to remove the flag once external kubelet credential provider promoted to GA
/kind deprecation
This issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
// TODO(#58034): This is not a static file, so it's not quite as straightforward as --google-json-key. // We need to figure out how ACR users can dynamically provide pull credentials before we can deprecate this. pflagRegister(global, local, "azure-container-registry-config") <ins> local.MarkDeprecated("azure-container-registry-config", "Use --image-credential-provider-config and --image-credential-provider-bin-dir to setup acr credential provider instead. Will be removed in a future release.") </ins> }