https://github.com/thecodingmachine/deeployer-cleanup-action
A Github action to delete a Kubernetes namespace
https://github.com/thecodingmachine/deeployer-cleanup-action
Last synced: 4 months ago
JSON representation
A Github action to delete a Kubernetes namespace
- Host: GitHub
- URL: https://github.com/thecodingmachine/deeployer-cleanup-action
- Owner: thecodingmachine
- Created: 2020-05-27T20:10:44.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2020-05-27T20:58:10.000Z (about 6 years ago)
- Last Synced: 2025-10-20T06:24:43.376Z (8 months ago)
- Size: 1.95 KB
- Stars: 0
- Watchers: 5
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Deeployer cleanup action
This Github action can be used to delete a Kubernetes action.
It works similarly to the [thecodingmachine/deeployer](https://github.com/thecodingmachine/deeployer/#usage-in-github-actions) action
except it will delete a whole Kubernetes namespace instead of deploying an application.
```deploy_workflow.yaml
name: Clean Kubernetes namespace
on:
- delete
jobs:
clean:
runs-on: ubuntu-latest
steps:
- name: Delete namespace
uses: thecodingmachine/deeployer@master
env:
KUBE_CONFIG_FILE: ${{ secrets.KUBE_CONFIG_FILE }}
with:
namespace: target-namespace
```
You will need to put the content of your Kubernetes configuration file in the `KUBE_CONFIG_FILE` secret on Github.
### Cleanup in a Google cloud Kubernetes cluster
If you are connecting to a Google Cloud cluster, instead of passing a `KUBE_CONFIG_FILE`, you will need to pass
this set of environment variables:
- `GCLOUD_SERVICE_KEY`
- `GCLOUD_PROJECT`
- `GCLOUD_ZONE`
- `GKE_CLUSTER`