Cause: The operator Created At timestamp format varies among operators as the API does not require a specific format.
Consequence: Created At timestamps display as they are entered for each operator, leading to differences in how they display in the console.
Fix: If the Created At timestamp is entered as a valid date, the console will now display it using the Timestamp component, making it consistent with how timestamps are displayed elsewhere in the console.
Result: The Created At timestamp displays in a consistent manner with other timestamps in the console, assuming the value entered is a valid date (note some are not and display the invalid string itself).
Dear Team,
The creation timestamps of every operator has a different format, just browsing a few of them will give you an idea. I think having a common format would improve user experience.
Some examples
Created At
2019-11-30 22:40:00
Created At
2019-01-24T15-33-43Z
Created At
Fri Jan 17 09:58:52 UTC 2020
Created At
02/04/2020
Thanks
Gokhan Yucegok
Hi Evan,
They are here;
OCP Webconsole -> operatorhub -> select an operator -> somewhere at the left hand side of an operator window.
The left hand side of the page goes on like this: "operator version", "capability level", "provider type" ... "created at"
BR
Gokhan
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4196