Michael Delzer Updated by Michael Delzer

Import Kubernetes cluster


Import Kubernetes cluster into Control Plane to become Platform Stack. Currently supported cluster types are:

  • k8s-aws - AgileStacks Kubernetes on AWS (stack-k8s-aws)
  • eks - AWS EKS
  • metal - Bare-metal

Cluster TLS auth is read from stdin in the order:

  • k8s-aws, metal - Client cert, Client key, CA cert (optional).
  • eks - CA cert

User-supplied FQDN must match Cloud Account’s base domain. If no FQDN is supplied, then the name is prepended to Environment’s Cloud Account base domain name to construct FQDN.

hub api import <k8s-aws | eks | metal> <name or FQDN> -e <id | environment name> [-m <id | template name>] < keys.pem [flags]


      --create-new-template       Do not reuse existing template, always create fresh one
--create-template Create adapter template if no existing template is found for reuse (default true)
--eks-cluster string EKS cluster native name
--eks-endpoint string EKS cluster API endpoint (discovered via AWS EKS API)
-e, --environment string Put cluster in Environment, supply name or id
-h, --help help for import
--k8s-endpoint string K8S cluster API endpoint, default to api.{domain}
--metal-endpoint string Bare-metal cluster API endpoint (ip[:port])
--metal-ingress-ip string Bare-metal cluster static ingress IP (default to IP of endpoint)
-m, --template string Use specified adapter template, by name or id
-w, --wait Wait for deployment and tail logs
Options inherited from parent commands
--all-warnings Repeat all warnings before [successful] exit (default true)
--api string Hub API service base URL, HUB_API (default "")
--aws_profile string AWS ~/.aws/credentials profile, AWS_PROFILE (default "agilestacks")
--aws_region string AWS region hint (for S3 state access), AWS_DEFAULT_REGION (default "us-east-2")
--aws_use_iam_role_credentials Try EC2 instance credentials (default true)
--cache string API cache file (default is $HOME/.automation-hub-cache.yaml)
--compressed Write gzip compressed files (default true)
--config string Config file (default is $HOME/.automation-hub.{yaml,json})
-d, --debug Print debug info. Or set HUB_DEBUG=1
--encrypted string Write encrypted files if HUB_CRYPTO_PASSWORD is set. true / false (default "if-password-set")
-f, --force Force operation despite of errors. Or set HUB_FORCE=1
--log-destination string stderr or stdout (default "stderr")
-t, --trace Print detailed trace info. Or set HUB_TRACE=1
-v, --verbose Verbose mode (default true)


Use remote Automation Hub API to access Control Plane, hub_api Click Here

How did we do?