astro deployment adopt

This command is available only if you’re authenticated to an Astro Private Cloud installation.

Adopt an existing operator-managed Airflow custom resource into Astro Private Cloud. Adopting creates the corresponding Deployment record in Astro Private Cloud. It also updates the custom resource. It reconfigures the ingress and the authentication for the Airflow UI. With --use-apc-logging, it also updates the logging configuration. The Deployment’s namespace and its metadata database don’t change.

Usage

astro deployment adopt --cluster-id=<cluster-id> --name=<cr-name> --namespace=<cr-namespace>

Options

Option	Description	Possible Values
`--accept-incompatibilities`	Adopt the Deployment even if the custom resource has fields with no Astro Private Cloud representation	`true` or `false`. The default value is `true`
`--cluster-id` (Required)	The ID of the cluster the Airflow custom resource is running on	Any valid cluster ID
`--description`	A description for the adopted Deployment	Any string
`-l`, `--label`	A label for the adopted Deployment. If omitted, Astro Private Cloud uses the `--name` value	Any string
`--name` (Required)	The `metadata.name` of the existing Airflow custom resource	Any string
`--namespace` (Required)	The Kubernetes namespace of the existing Airflow custom resource	Any string
`--use-apc-logging`	Route the adopted Deployment’s logs through Astro Private Cloud logging	None
`--use-apc-registry`	Use the Astro Private Cloud in-cluster registry for the adopted Deployment. You must pre-sync its images	None

Examples

astro deployment adopt --cluster-id=cmra8iy730008e519f0hma7nx --name=ce04 --namespace=ce04 --use-apc-logging --use-apc-registry --label="My custom label" --description="Adopted from standalone operator"

⌘I

Overview

Install the CLI

Develop with the CLI

Configure the CLI

Release information

Archived versions

astro deployment adopt

Usage

Options

Examples

​Usage

​Options

​Examples

​Related commands

Usage

Options

Examples

Related commands