porter connect
contains commands for connecting to external clusters and providers.
porter connect kubeconfig
current-context
that’s set in your default kubeconfig
(either by reading the $KUBECONFIG
env variable or reading from $HOME/.kube/config
). You can also pass a path to a kubeconfig file explicitly (see examples).
kubeconfig
file explicitly via:
kubectl config get-contexts
. For example, if there are two contexts named minikube
and staging
, you could connect both of them via:
certificate-authority
field, the CA data will be automatically populated.client-certificate
field, the certificate data will be automatically populated.client-key
field, the key data will be automatically populated.oidc
auth mechanism, and this mechanism requires OIDC issuer CA data via the idp-certificate-authority
field, the CA data will be automatically populated.token-file
field, the token data will be automatically populated.aws eks get-token
or aws-iam-authenticator
), the CLI will require an AWS IAM user that has permissions on the cluster. This user can be supplied manually or the Porter CLI can attempt to create this user automatically.gcp
auth mechanism (for connecting with GKE clusters), the CLI will require a GCP service-account
that has permissions to read from the GKE cluster. The CLI will ask the user if it can set this up automatically: if so, it will automatically detect the correct GCP project ID and will create a service account and download a key file. If the user does not wish the CLI to set this up automatically, the user will need to provide a file path to a service account key file that was downloaded from GCloud.porter connect dockerhub
porter connect docr
porter connect ecr
porter connect gcr
porter connect gar
porter connect registry
porter connect helm