gitlab-org--gitlab-foss/app/models/project_services
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
..
chat_message
asana_service.rb
assembla_service.rb
bamboo_service.rb
bugzilla_service.rb
buildkite_service.rb
builds_email_service.rb
campfire_service.rb
chat_notification_service.rb
ci_service.rb
custom_issue_tracker_service.rb
deployment_service.rb
discord_service.rb
drone_ci_service.rb
emails_on_push_service.rb
external_wiki_service.rb
flowdock_service.rb
gitlab_issue_tracker_service.rb
hangouts_chat_service.rb
hipchat_service.rb
irker_service.rb
issue_tracker_service.rb
jira_service.rb
kubernetes_service.rb Remove legacy Kubernetes #actual_namespace 2019-05-21 11:38:11 -05:00
mattermost_service.rb
mattermost_slash_commands_service.rb
microsoft_teams_service.rb
mock_ci_service.rb
mock_deployment_service.rb
mock_monitoring_service.rb
monitoring_service.rb
packagist_service.rb
pipelines_email_service.rb
pivotaltracker_service.rb
prometheus_service.rb
pushover_service.rb
redmine_service.rb
slack_service.rb
slack_slash_commands_service.rb
slash_commands_service.rb
teamcity_service.rb
youtrack_service.rb