Closed matti closed 5 years ago
Cannot reproduce this. Maybe it was really badly formatted yaml?
maybe, cant repro now either
@kke invalid kubeconfig causes this.
user:
auth-provider:
config:
access-token:
cmd-args: config config-helper --format=json
cmd-path: /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/gcloud
expiry: 2019-01-29T14:20:36Z
expiry-key: '{.credential.token_expiry}'
token-key: '{.credential.access_token}'
name: gcp
when I add quotes in expiry: 2019-01-29T14:20:36Z
--> expiry: '2019-01-29T14:20:36Z'
it works.
gcloud writes it like that
fun fact: brew install kontena/mortar/mortar
installed mortar works with this yaml, https://github.com/kontena/mortar/releases/download/v0.3.2/mortar-darwin-amd64-0.3.2 does not
I think 0.3.1 uses a version of k8s-client which uses load_stream
instead of safe_load_stream
.
If we just whitelist Time
, then it may bump into a problem when trying to create/apply a K8s::Resource
with an instance of Time
as value.
Yeah the problem is actually in k8s-client kubeconfig loader, not in mortar. Moving this there.
@kke @jakolehm https://github.com/kontena/k8s-client/pull/103 merged
can't wait to finally have gke support!
closed on k8s-client
with https://github.com/kontena/mortar/releases/download/v0.3.2/mortar-darwin-amd64-0.3.2