Context
Currently the operator logs are the only place where errors show up. These is a rather low level and not visible for regular users.
To improve this, the operator should expose errors and other information in the form of .status conditions and Kubernetes events.
See also:
Alternatives
An alternative would be to create a custom field in the object's status containing any error messages. While this might be easier to implement, it would not adhere to Kubernetes standards and makes it therefore harder to work with.
Context
Currently the operator logs are the only place where errors show up. These is a rather low level and not visible for regular users.
To improve this, the operator should expose errors and other information in the form of
.statusconditions and Kubernetes events.See also:
Alternatives
An alternative would be to create a custom field in the object's
statuscontaining any error messages. While this might be easier to implement, it would not adhere to Kubernetes standards and makes it therefore harder to work with.