-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for Azure BYOK exocompute (#205)
- Loading branch information
1 parent
910581c
commit 436fe66
Showing
20 changed files
with
822 additions
and
100 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| --- | ||
| # generated by https://github.com/hashicorp/terraform-plugin-docs | ||
| page_title: "polaris_azure_exocompute_cluster_attachment Resource - terraform-provider-polaris" | ||
| subcategory: "" | ||
| description: |- | ||
| The polaris_azure_exocompute_cluster_attachment resource attaches an Azure AKS | ||
| cluster to a customer managed host Exocompute configuration, allowing RSC to use | ||
| the cluster for Exocompute operations. | ||
| The cluster name must be specified as <resource-group>/<cluster-name>, e.g. | ||
| my-resource-group/my-cluster. | ||
| --- | ||
|
|
||
| # polaris_azure_exocompute_cluster_attachment (Resource) | ||
|
|
||
| The `polaris_azure_exocompute_cluster_attachment` resource attaches an Azure AKS | ||
| cluster to a customer managed host Exocompute configuration, allowing RSC to use | ||
| the cluster for Exocompute operations. | ||
|
|
||
| The cluster name must be specified as `<resource-group>/<cluster-name>`, e.g. | ||
| `my-resource-group/my-cluster`. | ||
|
|
||
|
|
||
|
|
||
| <!-- schema generated by tfplugindocs --> | ||
| ## Schema | ||
|
|
||
| ### Required | ||
|
|
||
| - `cluster_name` (String) Azure AKS cluster name. Changing this forces a new resource to be created. | ||
| - `exocompute_id` (String) RSC exocompute configuration ID (UUID). Changing this forces a new resource to be created. | ||
|
|
||
| ### Optional | ||
|
|
||
| - `token_refresh` (Number) To force a refresh of the authentication token, part of the connection command and manifest, increase the value of this field. The token is valid for 24 hours. | ||
|
|
||
| ### Read-Only | ||
|
|
||
| - `id` (String) RSC cluster ID (UUID). | ||
| - `manifest` (String) Kubernetes manifest which can be passed to `kubectl apply` to create a connection between the cluster and RSC. See `connection_command` for an alternative connection method. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,115 @@ | ||
| --- | ||
| # generated by https://github.com/hashicorp/terraform-plugin-docs | ||
| page_title: "polaris_azure_private_container_registry Resource - terraform-provider-polaris" | ||
| subcategory: "" | ||
| description: |- | ||
| The polaris_azure_private_container_registry resource enables the private | ||
| container registry (PCR) feature for the RSC customer account. This disables the | ||
| standard Rubrik container registry. | ||
| ~> Note: Even though the polaris_azure_private_container_registry resource | ||
| ID is an RSC cloud account ID, there can only be a single PCR per RSC | ||
| customer account. | ||
| Exocompute Image Bundles | ||
| The following GraphQL query can be used to retrieve information about the image | ||
| bundles used by RSC for exocompute: | ||
| graphql | ||
| query ExotaskImageBundle { | ||
| exotaskImageBundle { | ||
| bundleImages { | ||
| name | ||
| sha | ||
| tag | ||
| } | ||
| bundleVersion | ||
| eksVersion | ||
| repoUrl | ||
| } | ||
| } | ||
| The repoUrl field holds the URL to the RSC container registry from where the | ||
| RSC images can be pulled. | ||
| The following GraphQL mutation can be used to set the approved bundle version | ||
| for the RSC customer account: | ||
| graphql | ||
| mutation SetBundleApprovalStatus($input: SetBundleApprovalStatusInput!) { | ||
| setBundleApprovalStatus(input: $input) | ||
| } | ||
| The input is an object with the following structure: | ||
| json | ||
| { | ||
| "input": { | ||
| "approvalStatus": "APPROVED", | ||
| "bundleVersion": "1.164", | ||
| } | ||
| } | ||
| Where approvalStatus can be either APPROVED or REJECTED. bundleVersion | ||
| is the the bundle version being approved or rejected. bundleMetadata is | ||
| optional. | ||
| --- | ||
|
|
||
| # polaris_azure_private_container_registry (Resource) | ||
|
|
||
| The `polaris_azure_private_container_registry` resource enables the private | ||
| container registry (PCR) feature for the RSC customer account. This disables the | ||
| standard Rubrik container registry. | ||
|
|
||
| ~> **Note:** Even though the `polaris_azure_private_container_registry` resource | ||
| ID is an RSC cloud account ID, there can only be a single PCR per RSC | ||
| customer account. | ||
|
|
||
| ## Exocompute Image Bundles | ||
| The following GraphQL query can be used to retrieve information about the image | ||
| bundles used by RSC for exocompute: | ||
| ```graphql | ||
| query ExotaskImageBundle { | ||
| exotaskImageBundle { | ||
| bundleImages { | ||
| name | ||
| sha | ||
| tag | ||
| } | ||
| bundleVersion | ||
| eksVersion | ||
| repoUrl | ||
| } | ||
| } | ||
| ``` | ||
| The `repoUrl` field holds the URL to the RSC container registry from where the | ||
| RSC images can be pulled. | ||
|
|
||
| The following GraphQL mutation can be used to set the approved bundle version | ||
| for the RSC customer account: | ||
| ```graphql | ||
| mutation SetBundleApprovalStatus($input: SetBundleApprovalStatusInput!) { | ||
| setBundleApprovalStatus(input: $input) | ||
| } | ||
| ``` | ||
| The input is an object with the following structure: | ||
| ```json | ||
| { | ||
| "input": { | ||
| "approvalStatus": "APPROVED", | ||
| "bundleVersion": "1.164", | ||
| } | ||
| } | ||
| ``` | ||
| Where `approvalStatus` can be either `APPROVED` or `REJECTED`. `bundleVersion` | ||
| is the the bundle version being approved or rejected. `bundleMetadata` is | ||
| optional. | ||
|
|
||
|
|
||
|
|
||
| <!-- schema generated by tfplugindocs --> | ||
| ## Schema | ||
|
|
||
| ### Required | ||
|
|
||
| - `app_id` (String) Azure app registration application ID. Also known as the client ID. | ||
| - `cloud_account_id` (String) RSC cloud account ID (UUID). Changing this forces a new resource to be created. | ||
| - `url` (String) URL for customer provided private container registry. | ||
|
|
||
| ### Read-Only | ||
|
|
||
| - `id` (String) RSC cloud account ID (UUID). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.