Nader Ziada
Nader Ziada
the `identityRef` is part of the workload cluster definition, so that check would happen at the creation time of that cluster which would not help with the problem described here...
> I think that will be a common error case until `identityRef` is the only way. yes, makes sense
my main concern is that this is not consistent with other provider, so wondering if there is a way to add a prefix or something in the internal resource names...
@CecileRobertMichon is there anything else to do here?
/assign @shashwathi
/assign pivotal-nader-ziada
For Kaniko to be able to push to a Google Cloud Registry on a different project, it needs a Kubernetes secret, which contains the auth required to push the final...
The Kaniko build-template doesn't pick up the secret unless its in the format mentioned here: https://github.com/GoogleContainerTools/kaniko#kubernetes-secret Even if you have the secret, Kaniko doesn't read it. Using the custom template...
In the Kaniko docs here https://github.com/GoogleContainerTools/kaniko it says there are different methods of authentication based on the target registry
A simpler solution might be to do the following: * after adding the Build to the workqueue, also use AddAfter() to enqueue it again after the timeout duration * if...