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
Run skaffold in lab environment where access to internet is via proxy and use kaniko as image builder. Now skaffold spins up kaniko pod which doesn't have proxy set which results in base image pull failure, hence both kaniko and skaffold fails
Actual behavior
skaffold should run seamless irrespective of environment.
Possible Solution
Kaniko config should have http_proxy and https_proxy field and they should be passed as the environment variable to the kaniko pod.
apiVersion: skaffold/kind: Configbuild:
artifacts:
# denotes the user’s image push location in artifactory, ensure user write permission in artifactory, this should be the same location referenced in your respective deployment yml
- image: www.a.com/kube/pythonservercontext: .sync:
'*.py': .kaniko:
buildContext:
localDir: {}namespace: 103000-prash-devpodGracePeriodSeconds: 10dockerConfig:
path: C:\Users\prashant\.docker\config.jsondeploy:
kubectl:
manifests:
#must match the kubernetes deploy file name of application
- deploy.yml
Steps to reproduce the behavior
Run skaffold in lab environment where access to internet is via proxy
Skaffold fails at kaniko image building phase
The text was updated successfully, but these errors were encountered:
prary
changed the title
Proxy for kaniko pod while running in isolated environment
HTTP/HTTPs Proxy for kaniko pod while running in isolated environment
May 3, 2019
Expected behavior
Run skaffold in lab environment where access to internet is via proxy and use kaniko as image builder. Now skaffold spins up kaniko pod which doesn't have proxy set which results in base image pull failure, hence both kaniko and skaffold fails
Actual behavior
skaffold should run seamless irrespective of environment.
Possible Solution
Kaniko config should have http_proxy and https_proxy field and they should be passed as the environment variable to the kaniko pod.
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: