Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Minor
Fix Version/s: 1.2.0.GA
Affects Version/s: None
Component/s: documentation
Labels:
None

Story Points:
1
Affects:

Documentation (Ref Guide, User Guide, etc.)
Target Release:

1.2.0.GA

Sprint:
2019.5

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Dev story

As a Cluster Administrator, I want the YAML files provided to support multiple CRD versions so that I can take advantage of future OpenShift functionality, e.g. the ability to provide different schemas for each API version.

Investigate how to implement subresources / status in our CRDs

Do we need subresources for it
How should our Status fields look like
How do we support it in code (missing Fabric8 support)

Doc Requirements

Investigate how this will be documented for the 1.2.0 release. Consider the expected TOC.

is related to

ENTMQST-928 [DOC OCP] Document CRD Status - Broker Assignments for Topics (KafkaTopic Resource)

Closed

ENTMQST-929 [DOC OCP] Document CRD Status - Kafka broker address

Closed

relates to

ENTMQST-930 [DOC OCP] Document CRD versioning (v1alpha1 and v1beta1)

Closed

Assignee:: Paul Mellor

Reporter:: Paul Mellor

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2019/04/08 5:43 AM

Updated:: 2020/12/18 12:16 PM

Resolved:: 2019/04/12 3:31 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates