An error occurred fetching the project authors.
- 27 Jan, 2022 1 commit
-
-
Brian Williams authored
In 037420e3 we started associating security vulnerabilities with Kubernetes clusters via GraphQL. Vulnerabilities require developer permissions to view, while clusters require maintainer permissions to review. It doesn't make sense to be allowed to see the vulnerabilities in a cluster, but not other information about the cluster. So, this change makes cluster information available to developers. Changelog: changed
-
- 29 Jun, 2021 1 commit
-
-
Oghenerukevwe Kofi authored
-
- 13 Nov, 2020 1 commit
-
-
Petar Prokic authored
- Fix broken test - Add enabled and managed to PUT tests
-
- 10 Nov, 2020 1 commit
-
-
Petar Prokic authored
- Expose fields managed and enabled where missing - Update tests to use the new fields - Update handbook to mention the fields
-
- 29 Sep, 2020 1 commit
-
-
Hordur Freyr Yngvason authored
Adds the ability to use a namespace per project, instead of namespace per environment, for deployments using GitLab's Kubernetes integration. See https://gitlab.com/gitlab-org/gitlab/-/issues/38054
-
- 08 Jul, 2020 1 commit
-
-
Serena Fang authored
This will support the checkbox to enable/disable the Jira issues page. Display commits search in mobile & adjust text Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/214039 Update placeholder text per Pajamas guidelines (https://design.gitlab.com/components/search/) Unhide search bar in smaller screens.
-
- 23 Jun, 2020 1 commit
-
-
Arturo Herrero authored
The plan for RSpec 4.0 is to disable monkey patching, reference: https://rspec.info/blog/2013/07/the-plan-for-rspec-3/#zero-monkey-patching-mode https://relishapp.com/rspec/rspec-core/docs/configuration/zero-monkey-patching-mode This commit stops using RSpec monkey patching in several specs.
-
- 10 Apr, 2020 2 commits
-
-
Hordur Freyr Yngvason authored
In order to safely expose management_project_id on create we need to apply the same validations as we do on update.
-
Brad Downey authored
The docs for the POST method mention management_project_id but it was not supported, so we added it to the code. Conversely, docs for the PUT method were missing management_project_id, when it was in fact supported, so we added it to the docs.
-
- 28 Mar, 2020 1 commit
-
-
Peter Leitzen authored
We achieve this by using `let_it_be` where easy feasible and consolidating examples. Before: Finished in 41.21 seconds (files took 2.61 seconds to load) 41 examples, 0 failures After: Finished in 23.34 seconds (files took 2.82 seconds to load) 31 examples, 0 failures
-
- 26 Feb, 2020 1 commit
-
-
Peter Leitzen authored
243 files inspected, 539 offenses detected, 539 offenses corrected
-
- 12 Dec, 2019 1 commit
-
-
Adam Hegyi authored
The first of many MRs to make an attempt to have a test suite that can run successfully in any locale.
-
- 23 Oct, 2019 2 commits
-
-
Thong Kuah authored
Only allow cluster to update management_project to namespace (and descendants) of the cluster. For instance-level cluster, this is meaningless so skip for this cluster type.
-
Thong Kuah authored
For project and group cluster
-
- 07 Aug, 2019 1 commit
-
-
Tiger Watson authored
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.
-
- 11 Jul, 2019 2 commits
-
-
Dylan Griffith authored
The current approach requires catching exceptions to handle these errors and callers are already handling model validations so it seems more appropriate. Also it seemed to convoluted to add this logic directly to the model since the model needs to check too many possible associations to determine whether or not there are more than one cluster since the model doesn't know what it's being created on. Additionally we only wanted to validate during create to avoid the risk of existing models becoming invalid by many different edge cases.
-
Dylan Griffith authored
The current approach requires catching exceptions to handle these errors and callers are already handling model validations so it seems more appropriate. Also it seemed to convoluted to add this logic directly to the model since the model needs to check too many possible associations to determine whether or not there are more than one cluster since the model doesn't know what it's being created on. Additionally we only wanted to validate during create to avoid the risk of existing models becoming invalid by many different edge cases.
-
- 02 Jul, 2019 1 commit
-
-
Dylan Griffith authored
-
- 21 May, 2019 2 commits
-
-
Tiger authored
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).
-
Tiger authored
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).
-
- 03 May, 2019 1 commit
-
-
Mayra Cabrera authored
When this option is enabled, GitLab will create namespaces and service accounts as usual. When disabled, GitLab wont create any project specific kubernetes resources Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56557
-
- 05 Apr, 2019 1 commit
-
-
Thong Kuah authored
- rewords examples starting with 'should' - rewords examples starting with 'it' Note: I had to manually fixup "onlies" to "only"
-
- 01 Apr, 2019 1 commit
-
-
Mayra Cabrera authored
Domain was introduced on 11.8 and was not included on the Project Cluster API. With this change user will be able to include domain when adding and updating a cluster. Domain will also be included on the GET calls. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59441
-
- 20 Mar, 2019 1 commit
-
-
Tiger authored
The flag is on by default, but allows us to revert back to the old behaviour if we encounter any problems.
-
- 11 Jan, 2019 2 commits
-
-
Mayra Cabrera authored
-
Mayra Cabrera authored
Modifies authorize! method to accept a third param, and then use it in combination with 'add_cluster' policy to appropriately restrict adding multiple clusters Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56110
-
- 04 Jan, 2019 2 commits
-
-
Mayra Cabrera authored
Adds the following initial CRUD endpoints for Clusters API: - GET list of clusters - GET specific cluster - POST add existing cluster (mimic of "Add cluster") - PUT update cluser - DELETE destroy cluster Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40473
-
Mayra Cabrera authored
Overrides: - optional_params_ee to set environment_scope - create_cluster_user_params: To add environment_scope
-
- 02 Jan, 2019 1 commit
-
-
Mayra Cabrera authored
Adds the following initial CRUD endpoints for Clusters API: - GET list of clusters - GET specific cluster - POST add existing cluster (mimic of "Add cluster") - PUT update cluser - DELETE destroy cluster Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40473
-