1. 06 Dec, 2019 1 commit
  2. 04 Dec, 2019 1 commit
  3. 03 Dec, 2019 1 commit
  4. 19 Nov, 2019 1 commit
  5. 18 Nov, 2019 1 commit
  6. 16 Nov, 2019 1 commit
  7. 13 Nov, 2019 1 commit
  8. 08 Nov, 2019 2 commits
  9. 01 Nov, 2019 1 commit
  10. 30 Oct, 2019 1 commit
  11. 26 Oct, 2019 1 commit
  12. 24 Oct, 2019 1 commit
  13. 22 Oct, 2019 1 commit
  14. 23 Sep, 2019 1 commit
  15. 17 Sep, 2019 1 commit
  16. 13 Sep, 2019 1 commit
  17. 04 Sep, 2019 1 commit
  18. 30 Aug, 2019 1 commit
  19. 29 Aug, 2019 1 commit
  20. 28 Aug, 2019 1 commit
  21. 07 Aug, 2019 1 commit
    • Tiger Watson's avatar
      Use separate Kubernetes namespaces per environment · 6ddbfa68b32a
      Tiger Watson authored
      Kubernetes deployments on new clusters will now have
      a separate namespace per project environment, instead
      of sharing a single namespace for the project.
      
      Behaviour of existing clusters is unchanged.
      
      All new functionality is controlled by the
      :kubernetes_namespace_per_environment feature flag,
      which is safe to enable/disable at any time.
      6ddbfa68b32a
  22. 29 Jul, 2019 1 commit
  23. 16 Jul, 2019 1 commit
  24. 11 Jul, 2019 2 commits
    • Hordur Freyr Yngvason's avatar
      Give Knative serving permissions to service account · 0cfc54fefcd3
      Hordur Freyr Yngvason authored
      GitLab uses a kubernetes service account to perform deployments. For
      serverless deployments to work as expected with externally created
      clusters with their own knative installations (e.g. via Cloud Run), this
      account requires additional permissions in the serving.knative.dev API
      group.
      0cfc54fefcd3
    • Dylan Griffith's avatar
      Refactor: model errors for multi cluster validation · 0ba8f6b30227
      Dylan Griffith authored
      The current approach requires catching exceptions to handle these errors
      and callers are already handling model validations so it seems more
      appropriate.  Also it seemed to convoluted to add this logic directly to
      the model since the model needs to check too many possible associations
      to determine whether or not there are more than one cluster since the
      model doesn't know what it's being created on. Additionally we only
      wanted to validate during create to avoid the risk of existing models
      becoming invalid by many different edge cases.
      0ba8f6b30227
  25. 21 Jun, 2019 1 commit
    • Dylan Griffith's avatar
      Retry fetching Kubernetes Secret token · da58b0ea73c6
      Dylan Griffith authored
      Since Kubernetes is creating the Secret and token asynchronously it is
      necessary that we implement some delay or retrying logic to avoid a race
      condition where we fetch a Secret before the token is even set. There
      does not appear to be any way for us to force it to be set with any
      synchronous API call so retrying seems to be the only option.
      da58b0ea73c6
  26. 18 Jun, 2019 1 commit
    • Tiger's avatar
      Enable project-level JIT resource creation · 1c1961244115
      Tiger authored
      Previously this behaviour was only available to group
      and instance-level clusters, as some project clusters
      relied on Kubernetes credentials being passed through
      to the runner instead of having their resources managed
      by GitLab (which is not available when using JIT). These
      clusters have been migrated to unmanaged, so resources
      can be created on demand for the remaining managed clusters.
      1c1961244115
  27. 05 Jun, 2019 1 commit
  28. 17 May, 2019 1 commit
  29. 06 May, 2019 1 commit
  30. 03 May, 2019 1 commit
  31. 30 Apr, 2019 8 commits