more link updates and add 1.1 model schema

Author: markxnelson

site/v1.0/developer.md

@@ -65,7 +65,7 @@ To build the Javadoc for the operator, issue the following command:
 mvn javadoc:javadoc
 ```
 
-The Javadoc is also available in the GitHub repository [here](https://oracle.github.io/weblogic-kubernetes-operator/apidocs/index.html).
+The Javadoc is also available in the GitHub repository [here](https://oracle.github.io/weblogic-kubernetes-operator/v1.0/apidocs/index.html).
 
 ## Running integration tests
 

site/v1.1/apache.md

@@ -70,332 +70,170 @@ The generated Kubernetes YAML files look like the following, given the `domainUI
 Sample `weblogic-domain-apache.yaml` file for Apache HTTP Server deployment.
 
 ```
-
 --
-
 apiVersion: v1
-
 kind: ServiceAccount
-
 metadata:
-
   name: domain1-apache-webtier
-
   namespace: default
-
   labels:
-
     weblogic.domainUID: domain1
-
     weblogic.domainName: base_domain
-
     app: apache-webtier
-
 ---
-
 kind: Deployment
-
 apiVersion: extensions/v1beta1
-
 metadata:
-
   name: domain1-apache-webtier
-
   namespace: default
-
   labels:
-
     weblogic.domainUID: domain1
-
     weblogic.domainName: base_domain
-
     app: apache-webtier
-
 spec:
-
   replicas: 1
-
   selector:
-
     matchLabels:
-
       weblogic.domainUID: domain1
-
       weblogic.domainName: base_domain
-
       app: apache-webtier
-
   template:
-
     metadata:
-
       labels:
-
         weblogic.domainUID: domain1
-
         weblogic.domainName: base_domain
-
         app: apache-webtier
-
     spec:
-
       serviceAccountName: domain1-apache-webtier
-
       terminationGracePeriodSeconds: 60
-
       # volumes:
-
       # - name: "domain1-apache-webtier"
-
       #   hostPath:
-
       #     path: %LOAD_BALANCER_VOLUME_PATH%
-
       containers:
-
       - name: domain1-apache-webtier
-
         image: store/oracle/apache:12.2.1.3
-
         imagePullPolicy: Never
-
         # volumeMounts:
-
         # - name: "domain1-apache-webtier"
-
         #   mountPath: "/config"
-
         env:
-
           - name: WEBLOGIC_CLUSTER
-
             value: 'domain1-cluster-cluster-1:8001'
-
           - name: LOCATION
-
             value: '/weblogic'
-
         # - name: WEBLOGIC_HOST
-
         #   value: 'domain1-admin-server'
-
         # - name: WEBLOGIC_PORT
-
         #   value: '7001'
-
         readinessProbe:
-
           tcpSocket:
-
             port: 80
-
           failureThreshold: 1
-
           initialDelaySeconds: 10
-
           periodSeconds: 10
-
           successThreshold: 1
-
           timeoutSeconds: 2
-
         livenessProbe:
-
           tcpSocket:
-
             port: 80
-
           failureThreshold: 3
-
           initialDelaySeconds: 10
-
           periodSeconds: 10
-
           successThreshold: 1
-
           timeoutSeconds: 2
-
 ---
-
 apiVersion: v1
-
 kind: Service
-
 metadata:
-
   name: domain1-apache-webtier
-
   namespace: default
-
   labels:
-
     weblogic.domainUID: domain1
-
     weblogic.domainName: base_domain
-
 spec:
-
   type: NodePort
-
   selector:
-
     weblogic.domainUID: domain1
-
     weblogic.domainName: base_domain
-
     app: apache-webtier
-
   ports:
-
     - port: 80
-
       nodePort: 30305
-
       name: rest-https
-
 ```
 
 Sample `weblogic-domain-apache-security.yaml` file for associated RBAC roles and role bindings.
 
 ```
-
 ---
-
 kind: ClusterRole
-
 apiVersion: rbac.authorization.k8s.io/v1beta1
-
 metadata:
-
   name: domain1-apache-webtier
-
   labels:
-
     weblogic.domainUID: domain1
-
     weblogic.domainName: base_domain
-
 rules:
-
   - apiGroups:
-
       - ""
-
     resources:
-
       - pods
-
       - services
-
       - endpoints
-
       - secrets
-
     verbs:
-
       - get
-
       - list
-
       - watch
-
   - apiGroups:
-
       - extensions
-
     resources:
-
       - ingresses
-
     verbs:
-
       - get
-
       - list
-
       - watch
-
 ---
-
 kind: ClusterRoleBinding
-
 apiVersion: rbac.authorization.k8s.io/v1beta1
-
 metadata:
-
   name: domain1-apache-webtier
-
   labels:
-
     weblogic.domainUID: domain1
-
     weblogic.domainName: base_domain
-
 roleRef:
-
   apiGroup: rbac.authorization.k8s.io
-
   kind: ClusterRole
-
   name: domain1-apache-webtier
-
 subjects:
-
 - kind: ServiceAccount
-
   name: domain1-apache-webtier
-
   namespace: default
-
 ```
 
-
 Here are examples of the Kubernetes resources created by the WebLogic Operator:
 
-
 ```
-
 NAME                            DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
-
 bash-4.2$ kubectl get all |grep apache
-
 deploy/domain1-apache-webtier   1         1         1            1           2h
-
-
 rs/domain1-apache-webtier-7b8b789797   1         1         1         2h
-
-
 deploy/domain1-apache-webtier   1         1         1            1           2h
-
-
 rs/domain1-apache-webtier-7b8b789797   1         1         1         2h
-
-
-
 po/domain1-apache-webtier-7b8b789797-lm45z   1/1       Running   0          2h
-
-
 svc/domain1-apache-webtier                      NodePort    10.111.114.67    <none>        80:30305/TCP      2h
 
-
-
 bash-4.2$ kubectl get clusterroles |grep apache
-
 domain1-apache-webtier                                                 2h
 
-
-
 bash-4.2$ kubectl get clusterrolebindings |grep apache
-
 domain1-apache-webtier                                    2h
-
 ```
 
-
 It is sometimes, but rarely, desirable to expose a WebLogic Administration Server host and port through a load balancer to a public network.  If this is needed, you can customize the exposure of the WebLogic Administration Server host and port by using the `loadBalancerExposeAdminPort` property in the `create-weblogic-domain-inputs.yaml` file.
 
 ```
-
 # Boolean to indicate if the admin port is going to be exposed via APACHE load balancer. By default, it is false.
 loadBalancerExposeAdminPort: false
 ```
@@ -404,56 +242,36 @@ If the domain is created with the `loadBalancerExposeAdminPort` set to `true`, a
 
 ### Use your own plugin WL module configuration
 
-
 You can fine tune the behavior of the Apache plugin by providing your own Apache plugin configuration. You put your `custom_mod_wl_apache.conf` file in a local directory, for example, `<host-config-dir>` , and specify this location in the `create-weblogic-domain-inputs.yaml` file as follows:
 
 ```
-
 # Docker volume path for APACHE
-
 # By default, the VolumePath is empty, which will cause the volume mount be disabled
-
 loadBalancerVolumePath: <host-config-dir>
-
 ```
 
 After the `loadBalancerVolumePath` property is specified, the `create-weblogic-domain.sh` script will use the `custom_mod_wl_apache.conf` file in `<host-config-dir>` directory to replace what is in the Docker image.
 
 The generated YAML files will look similar except with un-commented entries like below:
 
 ```
-
       volumes:
-
       - name: "domain1-apache-webtier"
-
         hostPath:
-
           path: <host-config-dir>
-
       containers:
-
       - name: domain1-apache-webtier
-
         image: store/oracle/apache:12.2.1.3
-
         imagePullPolicy: Never
-
         volumeMounts:
-
         - name: "domain1-apache-webtier"
-
           mountPath: "/config"
-
 ```
 
-
-
 ## Use the Apache load balancer with a manually created WebLogic Domain
 
 If your WebLogic domain is not created by the WebLogic Operator, you need to manually create and start all Kubernetes' resources for the Apache HTTP Server.
 
-
   1. Create your own `custom_mod_wl_apache.conf` file, and put it in a local directory, for example, `<host-conf-dir>`. See the instructions in [Apache Web Server with Oracle WebLogic Server Proxy Plugin on Docker](https://docs.oracle.com/middleware/1213/webtier/develop-plugin/apache.htm#PLGWL395).
 
   2. Create the Apache deployment YAML file. See the example above. Note that you need to use the **volumes** and **volumeMounts** to mount `<host-config-dir>` into the `/config` directory inside the pod that runs the Apache web tier. Note that the Apache HTTP Server needs to be in the same Kubernetes namespace as the WebLogic domain that it needs to access.