101c4480b3
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). |
||
---|---|---|
.. | ||
chat_message | ||
asana_service_spec.rb | ||
assembla_service_spec.rb | ||
bamboo_service_spec.rb | ||
bugzilla_service_spec.rb | ||
buildkite_service_spec.rb | ||
campfire_service_spec.rb | ||
chat_notification_service_spec.rb | ||
custom_issue_tracker_service_spec.rb | ||
discord_service_spec.rb | ||
drone_ci_service_spec.rb | ||
emails_on_push_service_spec.rb | ||
external_wiki_service_spec.rb | ||
flowdock_service_spec.rb | ||
gitlab_issue_tracker_service_spec.rb | ||
hangouts_chat_service_spec.rb | ||
hipchat_service_spec.rb | ||
irker_service_spec.rb | ||
issue_tracker_service_spec.rb | ||
jira_service_spec.rb | ||
kubernetes_service_spec.rb | ||
mattermost_service_spec.rb | ||
mattermost_slash_commands_service_spec.rb | ||
microsoft_teams_service_spec.rb | ||
packagist_service_spec.rb | ||
pipelines_email_service_spec.rb | ||
pivotaltracker_service_spec.rb | ||
prometheus_service_spec.rb | ||
pushover_service_spec.rb | ||
redmine_service_spec.rb | ||
slack_service_spec.rb | ||
slack_slash_commands_service_spec.rb | ||
teamcity_service_spec.rb | ||
youtrack_service_spec.rb |