diff options
| author | Dylan Griffith <dyl.griffith@gmail.com> | 2018-11-28 15:29:01 +0300 |
|---|---|---|
| committer | Dylan Griffith <dyl.griffith@gmail.com> | 2018-11-30 13:03:42 +0300 |
| commit | e7f2be49d812079e1521dd7479ce4e8007afbf43 (patch) | |
| tree | 6c1b2f78eaf1903d403166d83f72bb48a4f166f2 /doc/user | |
| parent | 817bb1905703f0ae63c3a877348b7b4bcc1136c6 (diff) | |
Make KUBECONFIG nil if KUBE_TOKEN is nil
Having an invalid KUBECONFIG without a token in it is not helpful. This
only became possible recently now that we are creating a separate
namespace and service account (and hence token) to send to the runners.
This led to somewhat surprising results when troubleshooting
https://gitlab.com/gitlab-org/gitlab-ce/issues/53879 as I found that the
KUBECONFIG was still being passed but KUBE_TOKEN was not. These things
really should have been linked.
Furthermore now that we are also using the [presence of KUBECONFIG to
decide whether or not to run build steps in Auto
DevOps](https://gitlab.com/gitlab-org/gitlab-ce/blob/294d15be3e9497e7b67e1f9131ce9d5c0d68406c/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml#L164)
I think it makes even more sense to ensure that KUBECONFIG is a complete
config if passed to a job.
Diffstat (limited to 'doc/user')
0 files changed, 0 insertions, 0 deletions