36a01a88ce
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.
33 lines
1,012 B
Ruby
33 lines
1,012 B
Ruby
# frozen_string_literal: true
|
|
|
|
FactoryBot.define do
|
|
factory :cluster_kubernetes_namespace, class: Clusters::KubernetesNamespace do
|
|
association :cluster, :project, :provided_by_gcp
|
|
|
|
after(:build) do |kubernetes_namespace|
|
|
cluster = kubernetes_namespace.cluster
|
|
|
|
if cluster.project_type?
|
|
cluster_project = cluster.cluster_project
|
|
|
|
kubernetes_namespace.project = cluster_project.project
|
|
kubernetes_namespace.cluster_project = cluster_project
|
|
end
|
|
|
|
kubernetes_namespace.namespace ||=
|
|
Gitlab::Kubernetes::DefaultNamespace.new(
|
|
cluster,
|
|
project: kubernetes_namespace.project
|
|
).from_environment_slug(kubernetes_namespace.environment&.slug)
|
|
kubernetes_namespace.service_account_name ||= "#{kubernetes_namespace.namespace}-service-account"
|
|
end
|
|
|
|
trait :with_token do
|
|
service_account_token { FFaker::Lorem.characters(10) }
|
|
end
|
|
|
|
trait :without_token do
|
|
service_account_token nil
|
|
end
|
|
end
|
|
end
|