An error occurred fetching the project authors.
  1. 27 Jan, 2022 1 commit
    • Brian Williams's avatar
      Allow developers to read Kubernetes clusters · 722985df
      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
      722985df
  2. 29 Jun, 2021 1 commit
  3. 13 Nov, 2020 1 commit
    • Petar Prokic's avatar
      Fix tests · c4914b37
      Petar Prokic authored
      - Fix broken test
      - Add enabled and managed to PUT tests
      c4914b37
  4. 10 Nov, 2020 1 commit
    • Petar Prokic's avatar
      Update project clusters API · a86601bf
      Petar Prokic authored
      - Expose fields managed and enabled where missing
      - Update tests to use the new fields
      - Update handbook to mention the fields
      a86601bf
  5. 29 Sep, 2020 1 commit
  6. 08 Jul, 2020 1 commit
  7. 23 Jun, 2020 1 commit
  8. 10 Apr, 2020 2 commits
  9. 28 Mar, 2020 1 commit
    • Peter Leitzen's avatar
      Speed up request api specs for project clusters · cf0d2fa4
      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
      cf0d2fa4
  10. 26 Feb, 2020 1 commit
  11. 12 Dec, 2019 1 commit
  12. 23 Oct, 2019 2 commits
  13. 07 Aug, 2019 1 commit
    • Tiger Watson's avatar
      Use separate Kubernetes namespaces per environment · 36a01a88
      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.
      36a01a88
  14. 11 Jul, 2019 2 commits
    • Dylan Griffith's avatar
      Refactor: model errors for multi cluster validation · 8bc27d4c
      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.
      8bc27d4c
    • Dylan Griffith's avatar
      Refactor: model errors for multi cluster validation · dacd0ee1
      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.
      dacd0ee1
  15. 02 Jul, 2019 1 commit
  16. 21 May, 2019 2 commits
    • Tiger's avatar
      Remove legacy Kubernetes #actual_namespace · 98793c2e
      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).
      98793c2e
    • Tiger's avatar
      Remove legacy Kubernetes #actual_namespace · 101c4480
      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).
      101c4480
  17. 03 May, 2019 1 commit
  18. 05 Apr, 2019 1 commit
  19. 01 Apr, 2019 1 commit
  20. 20 Mar, 2019 1 commit
  21. 11 Jan, 2019 2 commits
  22. 04 Jan, 2019 2 commits
  23. 02 Jan, 2019 1 commit