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
The auto-generated API docs have precise and accurate info about API versions but do not provide direct, user-friendly information about how to populate the yaml file that users must create
The authored YAML CRD files need to provide specific information about apiVersions. In addition to the "Differences between versions" information, how do we represent the apiVersion info in the "YAML synopsis" and "Field description" blocks so it is meaningful to the users without creating a maintenance headache. Perhaps we could implement some sort of variable that always renders as the latest version of the API?
Some manual effort is always required when publishing docs for a new release. If we provide complete information in the reference page, we can minimize the amount of this information that is included in the rest of the documentation
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be
closed if no further activity occurs. Thank you for your contributions.
Part of #812
The text was updated successfully, but these errors were encountered: