You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment: Single Node Openshift (SNO) v4.16 for edge sites
Helm Chart version: akv2k8s v2.7.2
Deployed using ArgoCD which is part of Openshift GitOps Operator
Somehow passing the proxy variables in the deployment using ArgoCD did not work and we got the following error. The SNO cluster has a cluster wide proxy configured but Openshift requires that individual applications implement proxy using environment variables.
Akv2k8s pod startup error when a secret object is added: I0102 09:39:38.147960 1 worker.go:97] Error syncing key ace/conf-barauth: Failed to get secret for 'conf-barauth' from Azure Key Vault 'company-deep-test-vault': context deadline exceeded
Workaround: Only upon manually adding the "HTTP_PROXY", "HTTPS_PROXY" and "NO_PROXY" environment variables directly into the deployment "akv2k8s-controller" did it actually work.
Following is the ArgoCD app that successfully installed akv2k8s on target SNO cluster but did not add the PROXY environment variables above into the deployment "akv2k8s-controller".
Is this something you could fix in the helm chart?
Environment: Single Node Openshift (SNO) v4.16 for edge sites
Helm Chart version: akv2k8s v2.7.2
Deployed using ArgoCD which is part of Openshift GitOps Operator
Somehow passing the proxy variables in the deployment using ArgoCD did not work and we got the following error. The SNO cluster has a cluster wide proxy configured but Openshift requires that individual applications implement proxy using environment variables.
Akv2k8s pod startup error when a secret object is added:
I0102 09:39:38.147960 1 worker.go:97] Error syncing key ace/conf-barauth: Failed to get secret for 'conf-barauth' from Azure Key Vault 'company-deep-test-vault': context deadline exceeded
Workaround: Only upon manually adding the "HTTP_PROXY", "HTTPS_PROXY" and "NO_PROXY" environment variables directly into the deployment "akv2k8s-controller" did it actually work.
Following is the ArgoCD app that successfully installed akv2k8s on target SNO cluster but did not add the PROXY environment variables above into the deployment "akv2k8s-controller".
Is this something you could fix in the helm chart?
The text was updated successfully, but these errors were encountered: