Skip to content

Commit

Permalink
review comments part 2
Browse files Browse the repository at this point in the history
Signed-off-by: Ashley Davis <ashley.davis@venafi.com>
  • Loading branch information
SgtCoDFish committed Sep 20, 2023
1 parent 56811a3 commit 421f5f5
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion content/docs/projects/csi-driver.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,16 @@ directly into the pod, with no intermediate Secret being created.
- Fewer `Certificate` resources means writing less YAML
- Keys and certificates are destroyed when an application terminates
- No `Secret` resources needed for storing the certificate means less RBAC
- Great for ephemeral, short-lived certificates which don't need to survive a restart (e.g. certificates for mTLS)

## Why _not_ use csi-driver?

- If you need certificates to be persisted through a node restart
- If you need the same certificate to be shared by multiple components

## Installation

You must have a working installation of cert-manager present on your cluster and be running at least Kubernetes v1.16.
You must have a working installation of cert-manager present on your cluster and be running at least Kubernetes `v1.16`.

Instructions on how to install cert-manager can be found [on this website](../installation/README.md).

Expand Down

0 comments on commit 421f5f5

Please sign in to comment.