itcig/Deploy to GKE
Build Docker image and deploy app to k8s in GKE cloud.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Jun 2, 2022
- License
- MIT
Pinned Snippet
uses: itcig/action-deploy-gke@9cdd6c795e22298a6f8a45892d56dc00d7a72d9c # v1.7.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| project-id | The GCP project Id where the k8s cluster is hosted. | yes | — |
| gke-cluster | The name of the k8s cluster to deploy to. | yes | — |
| gke-zone | The GKE zone, e.g. 'us-east1-b'. | yes | — |
| app-slug | The root slug used for all k8s objects, typically the hyphenated hostname e.g. 'sitename-com' or 'subdomain-mysite-com'. | yes | — |
| app-variant | If deploying multiple versions of the same code, you can specify an additional variant beyond the slug e.g. 'division' or 'v2' | no | — |
| git-repo | The Github repository name. | yes | — |
| git-branch | The Git branch being pushed to. | yes | — |
| git-sha | The Git SHA that executed this workflow. | yes | — |
| gke-service-account-key | JSON key for IAM access to publish on GCR and deploy to GKE. | yes | — |
| docker-image-name | Specify a custom Docker image name instead of using the default GCR + Github repo name | no | — |
Outputs
no outputs