Skip to content
This repository has been archived by the owner on Jul 5, 2021. It is now read-only.

Releases: ContainerSolutions/externalsecret-operator

v0.2.0

25 Jan 14:25
f04c967
Compare
Choose a tag to compare

New Backends!

  • Azure Key Vault Backend
  • Credstash Backend

Fixes and repo improvements

  • Fixed latest tagging problem
  • Using Github Packages Registry now instead of Dockerhub

v0.2.0-crd-test2

25 Jan 14:34
Compare
Choose a tag to compare
v0.2.0-crd-test2 Pre-release
Pre-release
Rename types file

v0.1.0-test

25 Jan 13:59
Compare
Choose a tag to compare
v0.1.0-test Pre-release
Pre-release
Add schema to crds

v0.1.0

13 Nov 16:47
ff7cc01
Compare
Choose a tag to compare

0.1.0

  • Updated CRD
    • ExternalSecret
    • SecretStore
  • Support backends additions
    • gsm
  • Secret refresh (with refresh interval)
  • Binfile supported on aws
  • Multi keyed secrets
  • Removing 1password backend support

Fixes

#91:

  • Operator SDK updated to 1.0.1.

  • OPERATOR_NAME not used in new controller-runtime, using - - - LeaderElectionID instead
    deploy/ folder replaced with config/ which is handled by kustomize

  • CRD manifests in deploy/crds/ are now in config/crd/bases

  • CR manifests in deploy/crds/ are now in config/samples

  • Controller manifest deploy/operator.yaml is now in config/manager/manager.yaml

  • RBAC manifests in deploy are now in config/rbac/

  • Go updated to 1.15

  • Added tests to the externalsecret-controller

  • Helpers and options to work with webhooks
    use multigroup: true incase we need to support more complex secrets

  • Add config/backend-config to handle backend-config secrets
    Previous operator code in /legacy

  • #47 - Add Dockerfile build stage and use https://github.com/GoogleContainerTools/distroless - generated by operator-sdk

  • #3 - Introduce support for GCP secret manager(gsm) https://cloud.google.com/secret-manager/docs/configuring-secret-manager

  • #86 - Migrate to github actions from circle ci

  • #105

  • #97

  • #7 -Secret Binary Support

  • #92

  • #24

  • #106

  • #42

  • #29

Shoutouts to @iamcaleberic @jonatasbaldin @mircea-cosbuc @shinnlok @allanmoso @DonRenando @dbirks @ng29 for the contributions!

v0.1.0-alpha.1

05 Nov 15:58
25c9c8f
Compare
Choose a tag to compare
v0.1.0-alpha.1 Pre-release
Pre-release

this is a pre-release

0.1.0

  • Updated CRD
    • ExternalSecret
    • SecretStore
  • Support backends additions
    • gsm
  • Secret refresh (with refresh interval)
  • Binfile supported on aws
  • Multi keyed secrets

Fixes

#91:

  • Operator SDK updated to 1.0.1.

  • OPERATOR_NAME not used in new controller-runtime, using - - - LeaderElectionID instead
    deploy/ folder replaced with config/ which is handled by kustomize

  • CRD manifests in deploy/crds/ are now in config/crd/bases

  • CR manifests in deploy/crds/ are now in config/samples

  • Controller manifest deploy/operator.yaml is now in config/manager/manager.yaml

  • RBAC manifests in deploy are now in config/rbac/

  • Go updated to 1.15

  • Added tests to the externalsecret-controller

  • Helpers and options to work with webhooks
    use multigroup: true incase we need to support more complex secrets

  • Add config/backend-config to handle backend-config secrets
    Previous operator code in /legacy

  • #47 - Add Dockerfile build stage and use https://github.com/GoogleContainerTools/distroless - generated by operator-sdk

  • #3 - Introduce support for GCP secret manager(gsm) https://cloud.google.com/secret-manager/docs/configuring-secret-manager

  • #86 - Migrate to github actions from circle ci

  • #105

  • #97

  • #7 -Secret Binary Support

  • #92

  • #24

  • #106

  • #42

  • #29

Obs: 1password still has some problems. Were are releasing this as alpha so people can use the new documentation and new features, will release v0.1.0 proper release when 1password is fixed completely