Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/afritzler/gardener-gke
Using BASH Magic & Unicorns to setup a Gardener Landscape on a GKE Cluster
https://github.com/afritzler/gardener-gke
gardener gcp gke kubernetes
Last synced: 14 days ago
JSON representation
Using BASH Magic & Unicorns to setup a Gardener Landscape on a GKE Cluster
- Host: GitHub
- URL: https://github.com/afritzler/gardener-gke
- Owner: afritzler
- License: other
- Created: 2019-01-05T09:50:13.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2019-02-07T10:19:09.000Z (almost 6 years ago)
- Last Synced: 2024-11-10T07:45:07.150Z (2 months ago)
- Topics: gardener, gcp, gke, kubernetes
- Language: Shell
- Size: 183 KB
- Stars: 0
- Watchers: 6
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Gardener-GKE
_Disclaimer: This project sets up a Gardener landscape on a GKE cluster. This is by no means a productive setup!_
## Overview
## Prerequisites
* Kubernetes cluster
* Domain/Zone in CloudDNS
* GCP serviceaccount
* terraform
* jq
* cfssl
* openssl
* kubectl
* helm
## Setup
### Prepare setup.yaml
First we need to clone and configure our setup
```bash
git clone https://github.com/afritzler/gardener-gke.git
cd gardener-gke
cp setup.yaml.example setup.yaml
```
You will need a `kubeconfig` with basic-auth user authentication.
```bash
export KUBECONFIG=/tmp/kubeconfig
gcloud container clusters get-credentials CLUSTER_NAME --zone europe-west1-b --project PROJECT_NAME
src/bin/convertkubeconfig
```
Then, edit the `setup.yaml` accordingly.
### Deploy Etcd
Deploy the Etcd needed by the Gardener extension API server
```bash
src/etcd/deploy
```
### Deploy Ingress Controller + Ingress DNS Record
```bash
src/ingress-controller/deploy
```
### Deploy Gardener
Deploy the Gardener extension API server and controller
```bash
src/gardener/deploy
```
### Configure the Gardener Landscape
Deploy and configure CloudProfile, Seed, etc ...
```bash
src/gardenconfig/deploy
```
## Cleanup
### Shoots
Delete the created shoot cluster (a simple kubectl delete shoot NAME is not allowed in order to prevent users from accidentally deleting their clusters – instead, they need to confirm upfront that the deletion is fine by annotating the shoot resource. You can use this script to do that: https://github.com/gardener/gardener/blob/master/hack/delete (./hack/delete shoot gcp-test garden-core)).
To do it the manual way
```bash
kubectl -n garden-core annotate shoot gcp-test confirmation.garden.sapcloud.io/deletion=true --overwrite
kubectl -n garden-core delete shoot gcp-test
```
### Gardener Config
```bash
helm delete --purge gardenconfig
```
### Gardener
```bash
helm delete --purge gardener
```
### Etcd
```bash
helm delete --purge garden-etcd
```
### Ingress Controller
```bash
helm delete --purge nginx-ingress-controller
# to delete the DNS record
./src/ingress-controller/destroy
```