Joris Coenen 867e699030 Remove ready field from status ...

The usage of such a field is considered deprecated, conditions
should be used instead.

If there is a use-case that is not covered by conditions only
we can always reconsider adding an extra field to the status.

See the k8s guidelines for more details on the deprecation:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

2022-06-22 11:39:54 +02:00

..

apis

Remove ready field from status

2022-06-22 11:39:54 +02:00

controller

Remove ready field from status

2022-06-22 11:39:54 +02:00

kubernetessecrets

Merge remote-tracking branch 'origin/main' into item-status

2022-06-22 11:33:23 +02:00

mocks

Update tests and mock client

2022-03-24 12:13:34 +01:00

onepassword

Fix auto deployment restart dropping original pod annotations

2022-05-16 12:10:13 +02:00

utils

Auto restart one password custom resource will be be added to converted kubernetes secret

2021-03-03 14:29:27 -04:00