-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication to Azure Container Registry not working #568
Comments
Hi, thank you for reaching out to us. I followed the steps to reproduce but I am seeing the pods running successfully. Can you please provide additional logs and your workload yaml files if possible? |
I tried to upgrade to version 1.6.0. again. Here is the log from virtual-kubelet pod, after I triggered scaling event:
Here is a snippet of our k8s workload apiVersion: apps/v1
kind: Deployment
metadata:
name: service-context-aci-queue
namespace: app
labels:
service: service
context: context
queue: queue
app: app
spec:
selector:
matchLabels:
service: service
context: context
queue: queue
app: app
template:
metadata:
name: service-context-aci-queue
namespace: app
labels:
service: service
context: context
queue: queue
app: app
spec:
nodeSelector:
kubernetes.io/role: agent
beta.kubernetes.io/os: windows
type: virtual-kubelet
tolerations:
- key: virtual-kubelet.io/provider
operator: Exists
- key: azure.com/aci
effect: NoSchedule
containers:
- name: service-context
image: private.azurecr.io/app/service/context:latest
imagePullPolicy: Always
resources:
requests:
memory: "4Gi"
cpu: "1.0"
limits:
memory: "4Gi"
cpu: "1.0"
imagePullSecrets:
- name: regcred |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Issue
We are using .dockerconfigjson secrets to store credentials to private Azure Container Registry. After upgrade from 1.4.16 to 1.6.0, pods are unable to authenticate to ACR. Error from pod's logs is:
Steps To Reproduce
regcred
Expected behavior
Pod authenticates to private ACR and ACI is created.
Virtual-kubelet version
1.6.0
Kubernetes version
1.27.3
Additional context
Works as expected when reverted back to 1.4.16
The text was updated successfully, but these errors were encountered: