Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Beta documentation updates #146

Merged
merged 1 commit into from
Jun 7, 2024
+5 −1
Merged

Beta documentation updates #146

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion charts/sm-operator/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,8 @@

This chart is for the deployment of the Kubernetes Operator for Secrets Manager to different Kubernetes environments. The operator installs into your cluster and allows you to create a custom resource called a BitwardenSecret to synchronize secrets stored in Secrets Manager into your cluster as Kubernetes secrets.

***NOTE: This is a beta release and might be missing some functionality.***
> [!NOTE]
> This is a beta release and might be missing some functionality.

## Requirements

Expand Down Expand Up @@ -53,6 +54,9 @@ Update `containers.manager.image.tag` to use a different operator image version
- You can see help information for the `helm install` command by running `helm install --help`.
- You can see help information for the `helm upgrade` command by running `helm upgrade --help`.

> [!NOTE]
> While the chart is in beta, you will need to add the `--devel` flag to the `helm upgrade` command above.

## Creating BitwardenSecrets

Below is an example of creating a BitwardenSecret object to synchronsize secrets stored in Bitwarden Secrets Manager into Kubernetes secrets.
Expand Down
Loading