Unable to view Artifact Pull Secrets as option for Registry Endpoint in Azure IoT Operations

Question

In following this tutorial https://learn.microsoft.com/en-us/azure/iot-operations/develop-edge-apps/howto-configure-registry-endpoint?tabs=portal there should be an option for "Artifact Pull Secrets" as the authentication method for a Registry Endpoint. I do not see that option in my AIO Instance

Answer 1

Abby Greentree hi again )))) looks like it is ur day today )

the Artifact Pull Secrets option was available in earlier guidance, but in current versions the portal only exposes Anonymous, System assigned managed identity, and user assigned managed identity for registry endpoints. Artifact Pull Secrets are now handled at the Kubernetes level rather than directly in the AIO registry endpoint ui. In other words, AIO assumes either managed identity based access to ACR or anonymous access. If u want to use imagePullSecrets, u must create the Kubernetes secret manually in the target namespace and reference it in ur workload or connector deployment spec, not via the registry endpoint blade. So the fix is not a permission issue. Either switch to managed identity for ACR access, which is the recommended approach, or create a kubernetes.io/dockerconfigjson secret in the cluster and reference it in ur connector deployment yaml. The portal will not show Artifact Pull Secrets unless u are on a specific preview version that still exposes that path.

If u need to confirm, check the AIO extension version on the cluster and compare it with the doc version. The docs sometimes reflects preview features that are no longer surfaced in the GA portal UI.

rgds,

Alex