Section Number and Name:
Describe the issue:
Security context constraints are referenced in the kubernetes API
Suggestions for improvement:
They should be listed as an openshift object.
SCCs are OpenShift objects but for some historical reason they are accessed via /api, not /oapi. They can also be accessed via /apis/security.openshift.io, which is more reasonable.
It should be the case that object access via API groups will be documented correctly in 3.7, assuming that the new origin autogenerated docs will be branched.
I don't think the object location in the API docs should be changed, because in this case the docs are an accurate reflection of the API (even if it's not ideal!).
Adding a documentation note (i.e. updating https://github.com/openshift/origin/blob/master/pkg/security/apis/security/types.go#L17-L18) wouldn't hurt. Ping me if you need help doing this.
Thanks Jim for the explanation. Looks like this one is not a docs bug then. Closing it.