camel-k-kit-XXXXX is not able to inherit docker proxy configuration

[asifdxtreme]

camel-k-kit-XXXX is not able to use the docker proxy configuration from the host machine because of which the camel-ki-kit-XXX is not able to pull base image when running behind the proxy

[asifdxtreme]

IMO The proxy configuration should be passed onto kaniko is a similar way as done by GoogleContainerTools/skaffold#2283

[asifdxtreme]

camel-k-kit-XXX uses kaniko exector to pull the base image, kaniko exector has an option of using the proxy configuration provided in the path https://github.com/GoogleContainerTools/kaniko/blob/master/deploy/Dockerfile#L35, but this passing of values happens only while building the executor image, so if any one wants to put the proxy configurations in kaniko executor then you need to rebuild the image locally with the proxy configuration in your host machine and then let camel-k-operator use this image

[asifdxtreme]

camel-k-kit-XXX uses kaniko exector to pull the base image, kaniko exector has an option of using the proxy configuration provided in the path https://github.com/GoogleContainerTools/kaniko/blob/master/deploy/Dockerfile#L35, but this passing of values happens only while building the executor image, so if any one wants to put the proxy configurations in kaniko executor then you need to rebuild the image locally with the proxy configuration in your host machine and then let camel-k-operator use this image

this is the possible way of resolving the proxy issues in building phase