- Aug 01, 2018
-
-
Thong Kuah authored
Fix up VERSION for each of the applications * There is no 0.0.1 helm version for jupyterhub. Use the latest version instead * `:nginx` is not a valid chart version. Lock the ingress application GitLab installs to the latest chart version. * Use the latest gitlab-runner chart to prevent GitLab installing older versions when users have been installing the lastest version Always install from the VERSION and not the database `version` column. This should fix cases like https://gitlab.com/gitlab-org/gitlab-ee/issues/6795 in the instances where an install command failed previously, which locked the version in the database to an older version. Also, ensure that the version column is updated to the version we are installing. Add specs to show how previously failed appplications will be handled when the helm installation is run again Add changelog entry
-
- Jul 31, 2018
-
-
Mayra Cabrera authored
This reverts merge request !20801
-
- Jul 30, 2018
-
-
Dylan Griffith authored
-
Dylan Griffith authored
-
- Jul 28, 2018
-
-
Dylan Griffith authored
This is refactoring in the lead up to passing mutual TLS certs for helm applications. As such we expect all applications to need config files so we can remove the logic about which applications need and do not need this (ie `#config_map?`).
-
- Jun 20, 2018
-
-
Mayra Cabrera authored
-
- May 09, 2018
-
-
Matija Čupić authored
-
Kamil Trzcińśki authored
-
- Mar 29, 2018
-
-
Matija Čupić authored
-
- Mar 06, 2018
-
-
Mayra Cabrera authored
-
- Mar 01, 2018
-
-
Mayra Cabrera authored
-