actions-marketplace-validations/Scaleway Kustomize Deploy
Deploy to Scaleway using a Kustomize config
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Sep 1, 2022
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/jacobsvante_scaleway-kustomize-deploy-action@42c15eab47c76be095b47b72452c881031369c95 # no releases — HEAD as of 2026-07-13tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| secret-key | Scaleway secret key | yes | — |
| cluster-id | Scaleway Cluster ID. Can be retrieved with `scw k8s cluster list name=$CLUSTER_NAME -o template="{{.ID}}"`. | yes | — |
| region | Scaleway region (e.g. "fr-par") | yes | — |
| docker-namespace | Scaleway Docker registry namespace (e.g. "my-namespace") | yes | — |
| kustomization-base-dir | Path to base kustomize directory | yes | kustomize/base |
| kustomization-dir | Path to the kustomize directory to apply / deploy (e.g. `kustomize/overlays/production`) | yes | — |
| create-k8s-namespace | Create Kubernetes namespace if it does not exist | yes | true |
| image-name | Docker image name (e.g. `my-app`) | yes | — |
| image-tag | Docker image tag to deploy (e.g. `0.9.14`) | yes | — |
| age-secret-key | Secret key to decrypt deploy secrets with (e.g. `AGE-SECRET-KEY-123456`) | no | — |
| encrypted-filename | Filename/subpath inside `kustomization-dir` to a file with age encrypted secrets to decrypt | yes | secrets.env |
| decrypted-filename | Filename/subpath inside `kustomization-dir` to which the age encrypted secrets will be decrypted to | yes | secrets.env.dec |
| create-image-pull-secret | Create an image pull secret named "rg.`$region`.scw.cloud", to be referenced in `imagePullSecrets` in a k8s deployment/job | yes | true |
| k8s-dry-run | Used to set `kubectl` option `--dry-run` Valid values are `none` (default), `client` and `server`. | yes | none |
| pre-deploy-delete-job-selector | Delete objects with `status.successful=1` and the given label (e.g. `autodelete-successful-on-deploy=yes`), before doing the deploy. Useful for e.g. cleaning up a completed db migration job. | no | — |
Outputs
no outputs