Commit graph

4 commits

Author SHA1 Message Date
Tiger
e33ecfdec3 Disable JIT resource creation for project clusters
JIT resource creation blocks deployments if a user is
self-managing their cluster, as it will fail the build
if unable to create a namespace and service account.

Using a custom namespace and service account was previously
supported for project level clusters, so we should preserve
this functionality.

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27352
2019-04-16 13:59:37 +10:00
Thong Kuah
e3188eb13e Shift to class methods for RefreshService
As we don't use any instance attributes and we don't seem to have any
commonalities between the cluster and the project variant.
2018-12-05 11:57:02 +13:00
Thong Kuah
9c140b7d26 DRY up refresh service
The two pieces of code are identical so use a private method
2018-12-05 10:16:44 +13:00
Thong Kuah
d54791e094 Create k8s namespace for project in group clusters
AFAIK the only relevant place is Projects::CreateService, this gets
called when user creates a new project, forks a new project and does
those things via the api.

Also create k8s namespace for new group hierarchy
when transferring project between groups

Uses new Refresh service to create k8s namespaces

- Ensure we use Cluster#cluster_project

If a project has multiple clusters (EE), using Project#cluster_project
is not guaranteed to return the cluster_project for this cluster. So
switch to using Cluster#cluster_project - at this stage a cluster can
only have 1 cluster_project.

Also, remove rescue so that sidekiq can retry
2018-12-05 10:16:44 +13:00