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
Joris Coenen
00436b4aee
Place back description in CRD
...
This comment was placed manually and therefore
disappeared when regenerating the CRDs.
2022-06-21 14:38:48 +02:00
Joris Coenen
6c20db47d6
Add Status field to OnePasswordItem resource
...
This makes it easier to see whehter the controller
succeeded in creating the Kubernetes secret for a
OnePasswordItem. If something failed, the `ready` field
will be `false` and the `OnePasswordItemReady` condition
will have a `status` of `False` with the error messages
in the `message` field.
2022-06-15 17:46:56 +02:00
Andres Montalban
5d229c42d5
feat: Allow configuration of the Kubernetes Secret type to be created
2021-11-18 08:32:55 -03:00
jillianwilson
824f54b4fa
Initial 1Password Operator commit
2020-12-10 18:28:38 -04:00
