Skip to content

Commit

Permalink
Merge #135
Browse files Browse the repository at this point in the history
135: Add a note about the secret type bug r=anguslees a=johnraz

I just got bitten by the bug in #86 and #92 and lost quite a bit of time finding out what was happening.
This will hopefully help other people figure it out faster until the proper fix is released.

Co-authored-by: Jonathan Liuti <liuti.john@gmail.com>
  • Loading branch information
bors[bot] and johnraz committed Dec 18, 2018
2 parents 87dcea3 + 0afe7f7 commit e8e19e5
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,8 @@ the generic documentation for more information on the process.

## Usage

**WARNING**: A bug in the current version is limiting secrets to use the "opaque" type. If you need to use another secret type (eg: `kubernetes.io/dockerconfigjson`), please use kubeseal from release 0.5.1 until [#86](https://github.com/bitnami-labs/sealed-secrets/issues/86) and [#92](https://github.com/bitnami-labs/sealed-secrets/issues/92) are resolved.

```sh
# Create a json/yaml-encoded Secret somehow:
# (note use of `--dry-run` - this is just a local file!)
Expand Down

0 comments on commit e8e19e5

Please sign in to comment.