kubermatic
kubermatic copied to clipboard
Add project-aware cloud provider endpoints for EKS
What this PR does / why we need it: This PR adds new API endpoints for EKS that are project-aware, which means they are capable of using project-scoped presets (using a Preset with project restrictions via the existing API endpoints is not possible).
Which issue(s) this PR fixes:
Fixes #11164
What type of PR is this? /kind feature /kind api-change
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Add API endpoints `/api/v2/projects/{project_id}/providers/eks/amitypes`, `/api/v2/projects/{project_id}/providers/eks/capacitytypes`, `/api/v2/projects/{project_id}/providers/eks/clusterroles`, `/api/v2/projects/{project_id}/providers/eks/regions`, `/api/v2/projects/{project_id}/providers/eks/securitygroups`, `/api/v2/projects/{project_id}/providers/eks/subnets`, `/api/v2/projects/{project_id}/providers/eks/validatecredentials`, `/api/v2/projects/{project_id}/providers/eks/versions`, `/api/v2/projects/{project_id}/providers/eks/vpcs` for EKS that allow using project-scoped Presets as credentials
Documentation:
NONE
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: embik
Once this PR has been reviewed and has the lgtm label, please assign pkprzekwas for approval by writing /assign @pkprzekwas in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
- ~~OWNERS~~ [embik]
- cmd/kubermatic-api/OWNERS
- pkg/handler/OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest
/hold
For api migration.