From ee9cf02311fecdb9d400d306eabe34f7c2f053eb Mon Sep 17 00:00:00 2001 From: Michael Bridgen Date: Mon, 14 Jan 2019 13:15:00 +0000 Subject: [PATCH] Note k8s 1.13.0 secret creation issue In troubleshooting.md, rather than FAQs, on a mental coin flip. --- site/troubleshooting.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/site/troubleshooting.md b/site/troubleshooting.md index 268642977..4e084029b 100644 --- a/site/troubleshooting.md +++ b/site/troubleshooting.md @@ -72,3 +72,14 @@ GCP (in general) has quite conservative API rate limiting, and Flux's default settings can bump API usage over the limits. See [weaveworks/flux#1016](https://github.com/weaveworks/flux/issues/1016) for advice. + +### Flux doesn't seem to be able to use my imagePullSecrets + +If you're using `kubectl` v1.13.x to create them, then it may be due +to [this problem](https://github.com/weaveworks/flux/issues/1596). In +short, there was a breaking change to how `kubectl` creates secrets, +that found its way into the Kubernetes 1.13.0 release. It has been +corrected in [kubectl +v1.13.2](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.13.md#changelog-since-v1131), +so using that version or newer to create secrets should fix the +problem.