You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An important goal for OLM v1 is to not have users guess what the result of creating/updating/deleting a certain olm owned resource was. Eg, when I (an admin) create a scopedInstance, what does a Successful condition on the scopedInstance CR really mean? Without any information on the resources created, I need to ref a copy of the scopedTemplate CR, go down the list in the socpedTemplate.spec and kubectl describe roles/clusterroles/bindings etc to ensure there wasn't an issue creating any of the resources + there resources created are truly the ones I allowed.
I would like to have information about what changed on cluster (what got created/deleted/updated etc), so that I don't have to do a reference based audit of there resources. Also, if there's any issue while creating the resources, I'd like that information surfaced in a digestible way too.
The text was updated successfully, but these errors were encountered:
An important goal for OLM v1 is to not have users guess what the result of creating/updating/deleting a certain olm owned resource was. Eg, when I (an admin) create a scopedInstance, what does a
Successful
condition on the scopedInstance CR really mean? Without any information on the resources created, I need to ref a copy of the scopedTemplate CR, go down the list in the socpedTemplate.spec andkubectl describe
roles/clusterroles/bindings etc to ensure there wasn't an issue creating any of the resources + there resources created are truly the ones I allowed.I would like to have information about what changed on cluster (what got created/deleted/updated etc), so that I don't have to do a reference based audit of there resources. Also, if there's any issue while creating the resources, I'd like that information surfaced in a digestible way too.
The text was updated successfully, but these errors were encountered: