Commit Graph

10 Commits

Author SHA1 Message Date
Joris Coenen
afa076d321 Stop copying annotations from OnePasswordItem and Deployment to Secret
There is no reason for random annotations to be carried over. This
can lead to weird problems like the `kubectl.kubernetes.io/last-applied-configuration`
annotation ending up on a Secret.
2022-04-11 15:55:28 +02:00
Xabier Larrakoetxea
79868ae374 Add owner reference to the created secrets
Signed-off-by: Xabier Larrakoetxea <me@slok.dev>
2022-04-05 20:31:42 +02:00
Andres Montalban
5d229c42d5 feat: Allow configuration of the Kubernetes Secret type to be created 2021-11-18 08:32:55 -03:00
mcmarkj
f241d7423d Use deepequal 2021-08-19 16:11:29 +01:00
mcmarkj
bd96d50a9b Add Labels & Annotations from OPObject to Secret 2021-05-28 16:39:00 +01:00
jillianwilson
62ca0c25fd Making casing of annotations consistent 2021-04-09 10:41:41 -03:00
jillianwilson
d98f9172a0 Auto restart one password custom resource will be be added to converted kubernetes secret 2021-03-03 14:29:27 -04:00
jillianwilson
0824aa0837 Refactoring map of updated secrets to include secret 2021-02-26 10:45:30 -04:00
jillianwilson
76ee62519e Ignore restart annotation when looking for 1Password annotations 2021-01-13 15:32:03 -04:00
jillianwilson
824f54b4fa Initial 1Password Operator commit 2020-12-10 18:28:38 -04:00