Kaniko for InCluster Builder cannot connect to Minio Service

[swiftdiaries]

/kind bug

What steps did you take and what happened:
Created a MinioContextSource for the in-cluster builder.
Executed the image builder.

Logs from the fairing job:

k logs -n anonymous fairing-builder-rtqch-287mg
Error: error resolving source context: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

What did you expect to happen:
Image to be built and pushed to registry successfully.

Anything else you would like to add:
It's probably because I need to mount the credentials needed for the Minio Server.

Environment:

• Fairing version: (use python -c "import kubeflow.fairing; print(kubeflow.fairing.__version__)"):
• Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard): v1.0.0-rc4
• Kubernetes version: (use kubectl version): v1.14.10
• OS (e.g. from /etc/os-release):

NOTE: If you are using fair from master, please provide us the git commit hash.

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
kind/bug	0.99

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[swiftdiaries]

Related: #456

[swiftdiaries]

Adding this as an issue to track problems with running an in-cluster builder on vanilla k8s. Might not be a direct bug in fairing.

[swiftdiaries]

GoogleContainerTools/kaniko#698
This has the right podspec for building with Minio Contexts.
I'll update #458 with the changes