diff options
| author | Tiger Watson <twatson@gitlab.com> | 2019-08-07 07:40:29 +0300 |
|---|---|---|
| committer | Thong Kuah <tkuah@gitlab.com> | 2019-08-07 07:40:29 +0300 |
| commit | 36a01a88ce4c35f3d2b455c7943eeb9649b51163 (patch) | |
| tree | e568be9b9b80626b60f8e0e445ea95ee570e9523 /spec/requests | |
| parent | 54377159730c676bd40b64e66acfb57faf90eabf (diff) | |
Use separate Kubernetes namespaces per environment
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.
Diffstat (limited to 'spec/requests')
| -rw-r--r-- | spec/requests/api/project_clusters_spec.rb | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/spec/requests/api/project_clusters_spec.rb b/spec/requests/api/project_clusters_spec.rb index e8ed016db69..a7b919de2ef 100644 --- a/spec/requests/api/project_clusters_spec.rb +++ b/spec/requests/api/project_clusters_spec.rb @@ -336,7 +336,6 @@ describe API::ProjectClusters do it 'does not update cluster attributes' do expect(cluster.domain).not_to eq('new_domain.com') expect(cluster.platform_kubernetes.namespace).not_to eq('invalid_namespace') - expect(cluster.kubernetes_namespace_for(project)).not_to eq('invalid_namespace') end it 'returns validation errors' do |