Merge pull request #180 from oracle/docfix

Doc fixes

Author: rjeberhard

README.md

@@ -59,7 +59,7 @@ Oracle recommends careful consideration before deciding to expose any administra
 
 The Oracle WebLogic Server Kubernetes Operator has the following requirements:
 
-*	Kubernetes 1.7.5+, 1.8.0+ (check with `kubectl version`).  Note that Kubernetes 1.9.x is not supported yet.
+*	Kubernetes 1.7.5+, 1.8.0+, 1.9.0+, 1.10.0 (check with `kubectl version`).
 *	Flannel networking v0.9.1-amd64 (check with `docker images | grep flannel`)
 *	Docker 17.03.1.ce (check with `docker version`)
 *	Oracle WebLogic Server 12.2.1.3.0

site/design.md

@@ -21,6 +21,17 @@ The operator is designed with security in mind from the outset.  Some examples o
 
 The operator is designed to avoid imposing any arbitrary restriction on how WebLogic Server may be configured or used in Kubernetes.  Where there are restrictions, these are based on the availability of some specific feature in Kubernetes; for example, multicast support.
 
-The operator learns of WebLogic domains through instances of a domain Kubernetes resource.  When the operator is installed, it creates a Kubernetes [Custom Resource Definition](https://kubernetes.io/docs/concepts/api-extension/custom-resources/).  This custom resource definition defines the domain resource type.  Once this type is defined, you can manage domain resources using `kubectl` just like any other resource type.  For instance, `kubectl get domain` or `kubectl edit domain domain1`.  The schema for domain resources is [here](../swagger/domain.json).
+The operator learns of WebLogic domains through instances of a domain Kubernetes resource.  When the operator is installed, it creates a Kubernetes [Custom Resource Definition](https://kubernetes.io/docs/concepts/api-extension/custom-resources/).  This custom resource definition defines the domain resource type.  Once this type is defined, you can manage domain resources using `kubectl` just like any other resource type.  For instance, `kubectl get domain` or `kubectl edit domain domain1`.  
+
+Schema for domain resources:
+* [Domain](../model/src/main/resources/schema/domain.json)
+* [DomainSpec](../model/src/main/resources/schema/spec.json)
+* [ServerStartup](../model/src/main/resources/schema/serverstartup.json)
+* [ClusterStartup](../model/src/main/resources/schema/clusterstartup.json)
+* [DomainStatus](../model/src/main/resources/schema/status.json)
+* [DomainCondition](../model/src/main/resources/schema/condition.json)
+* [ServerStatus](../model/src/main/resources/schema/serverstatus.json)
+* [ServerHealth](../model/src/main/resources/schema/serverhealth.json)
+* [SubsystemHealth](../model/src/main/resources/schema/subsystemhealth.json)
 
 The schema for the domain resource is designed to be as sparse as possible.  It includes the connection details for the Administration Server, but all of the other content are operational details about which servers should be started, environment variables, and details about what should be exposed outside the Kubernetes cluster.  This way, the WebLogic domain's configuration remains the normative configuration.