Tiger 101c4480b3 Remove legacy Kubernetes #actual_namespace ... When Kubernetes clusters were originally built they could only exist at the project level, and so there was logic included that assumed there would only ever be a single Kubernetes namespace per cluster. We now support clusters at the group and instance level, which allows multiple namespaces. This change consolidates various project-specific fallbacks to generate namespaces, and hands all responsibility to the Clusters::KubernetesNamespace model. There is now no concept of a single namespace for a Clusters::Platforms::Kubernetes; to retrieve a namespace a project must now be supplied in all cases. This simplifies upcoming work to use a separate Kubernetes namespace per project environment (instead of a namespace per project).		2019-05-21 11:38:11 -05:00
..
kubernetes_spec.rb	Remove legacy Kubernetes #actual_namespace	2019-05-21 11:38:11 -05:00