Tiger Watson 36a01a88ce 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.		2019-08-07 04:40:29 +00:00
..
api	Use separate Kubernetes namespaces per environment	2019-08-07 04:40:29 +00:00
projects	Fix plan stage query	2019-06-17 13:17:18 +00:00
git_http_spec.rb	Added write_repository scope for personal access token	2019-04-15 13:05:55 +00:00
jwt_controller_spec.rb	Added write_repository scope for personal access token	2019-04-15 13:05:55 +00:00
lfs_http_spec.rb	Cleanup usages of JSON.parse in specs	2019-07-16 08:03:49 +00:00
lfs_locks_api_spec.rb	Cleanup usages of JSON.parse in specs	2019-07-16 08:03:49 +00:00
oauth_tokens_spec.rb
openid_connect_spec.rb	Remove code related to object hierarchy in MySQL	2019-07-25 15:35:06 +08:00
rack_attack_global_spec.rb	Include user id and username in auth log	2019-07-02 19:48:06 +00:00
request_profiler_spec.rb	Add profile mode to extend request profiling	2019-07-18 23:11:08 +10:00
user_activity_spec.rb