Ansible-based Operators automatically update custom resource (CR)
status subresources with generic information about the previous Ansible run. This includes the number of successful and failed tasks and relevant error messages as shown:
message: 'Status code was -1 and not : Request failed: <urlopen error [Errno
113] No route to host>'
- lastTransitionTime: 2018-12-03T13:46:13Z
message: Running reconciliation
Ansible-based Operators also allow Operator authors to supply custom status values with the
k8s_status Ansible module, which is included in the
operator_sdk.util collection. This allows the author to update the
status from within Ansible with any key-value pair as desired.
By default, Ansible-based Operators always include the generic Ansible run output as shown above. If you would prefer your application did not update the status with Ansible output, you can track the status manually from your application.