Read about our upcoming Code of Conduct on this issue

  1. 06 Dec, 2019 1 commit
  2. 03 Dec, 2019 1 commit
  3. 23 Sep, 2019 1 commit
  4. 28 Aug, 2019 1 commit
  5. 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.
  6. 27 Jun, 2019 2 commits
    • Thong Kuah's avatar
      Drop fallback to deployment platform · 68b6a39d85db
      Thong Kuah authored
      All deployments should have already their cluster_id filled in on
      creation. Legacy deployments will not be retried as:-
      * Ci::Build#retry calls `Ci::RetryBuildService`
      * Ci::Pipeline#retry
      calls `Ci::RetryPipelineService` which also calls
      * `Ci::RetryBuildService` will clone a build to retry
      It is also impossibly to backfill Deployment#cluster_id from
      Project#deployment_platform correctly as clusters could have been
      deleted, added or altered in the intervening time.
    • Thong Kuah's avatar
      Use deployment's cluster for kubernetes prereq · 6178516bbfec
      Thong Kuah authored
      A deployment will have a cluster associated on creation if there is one.
      Otherwise fallback to deployment_platform for legacy deployments.
  7. 24 Jun, 2019 1 commit
  8. 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.
  9. 14 Jun, 2019 1 commit
  10. 03 May, 2019 1 commit
  11. 16 Apr, 2019 1 commit
  12. 20 Mar, 2019 3 commits
    • Tiger's avatar
      Don't recreate Kubernetes namespaces if they exist · 77daff697129
      Tiger authored
      Instead of attempting to create or update a Kubernetes
      namespace on every deploy, only do so when we know it
      doesn't exist yet.
    • Tiger's avatar
      Create one Kubernetes namespace for a deployment · c57e575b630d
      Tiger authored
      Instead of creating a Kubernetes namespace on every
      cluster related to a project, only create one on the
      cluster the project is about to be deployed to.
    • Tiger's avatar
      Add build prerequisite for Kubernetes namespaces · 7ca1716dfa60
      Tiger authored
      Builds that have deployments require Kubernetes resources
      to be created before the build can be deployed. These
      resources are no longer created when the cluster is
      created, which allows us to only create the resources
      required by each specific build.