Skip to content

Commit

Permalink
added velero components
Browse files Browse the repository at this point in the history
  • Loading branch information
Akshit8 committed Feb 24, 2021
1 parent 776c512 commit 7711451
Show file tree
Hide file tree
Showing 3 changed files with 37 additions and 0 deletions.
37 changes: 37 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,43 @@ mv /tmp/velero-v1.5.1-linux-amd64/velero /usr/local/bin/velero
chmod +x /usr/local/bin/velero
```

## Deploying Kubernetes objects in a sample namespace
Kubernetes object that I use for this tutorial is located in [k8s-objects](./k8s-objects) folder.

```bash
kubectl create ns sample

kubectl -n sample apply -f ./k8s-objects
```

<img src="assets/samplens.png">

<img src="assets/samplens2.png">

## Configuring Velero for backing-up sample namespace

- Using Velero CLI that we installed previously, we need to deploy some components(that velero use) inside our cluster and configure them, so that velero can access our cloud storage bucket

```bash
# setting the bucket name
export BUCKET=velero-akshit

# installing velero with provider gcp
velero install \
--provider gcp \
--plugins velero/velero-plugin-for-gcp:v1.1.0 \
--bucket $BUCKET \
--secret-file ./gcpServiceAccount/credentials.json
```

To verify above installation run following commands

```bash
root@my-vm:/work# kubectl -n velero get pods
NAME READY STATUS RESTARTS AGE
velero-86bb45cdfb-987ps 1/1 Running 0 23s
```



## Author
Expand Down
Binary file added assets/samplens.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added assets/samplens2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 7711451

Please sign in to comment.