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
Our operator has significant responsibility in the UDS stack and creates a number of child resources during reconciliation of a Package. We would like to document/diagram visually the resource stack that corresponds with pieces of a Package spec, i.e. a given expose entry will create a virtualservice and serviceentry. This diagram should be created in code ideally, or at least in an easily editable format so that it can be updated in the future when pieces of the Package spec change.
Stylistically it may be helpful to review this diagram from Pepr which has a similar style of drawing connections from the "code" (in our case Package spec) to the effect (in our case created resources).
Definition of done: Diagram of what is produced from the Package reconciliation, mapped visually to the spec of the Package CR.
The text was updated successfully, but these errors were encountered:
Our operator has significant responsibility in the UDS stack and creates a number of child resources during reconciliation of a Package. We would like to document/diagram visually the resource stack that corresponds with pieces of a
Package
spec, i.e. a givenexpose
entry will create avirtualservice
andserviceentry
. This diagram should be created in code ideally, or at least in an easily editable format so that it can be updated in the future when pieces of the Package spec change.Stylistically it may be helpful to review this diagram from Pepr which has a similar style of drawing connections from the "code" (in our case
Package
spec) to the effect (in our case created resources).Definition of done: Diagram of what is produced from the Package reconciliation, mapped visually to the spec of the Package CR.
The text was updated successfully, but these errors were encountered: