adding version warnings and checking all links

Author: markxnelson

site/v1.0/apache.md

@@ -73,375 +73,195 @@ 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
-
 ```
 
-
 ### 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.

site/v1.0/architecture.md

@@ -1,3 +1,5 @@
+> **WARNING** This documentation is for version 1.0 of the operator.  To view documenation for the current release, [please click here](/site).
+
 # Architectural overview
 
 The operator consists of the following two main parts:

site/v1.0/creating-domain.md

@@ -1,3 +1,5 @@
+> **WARNING** This documentation is for version 1.0 of the operator.  To view documenation for the current release, [please click here](/site).
+
 # Creating a WebLogic domain
 
 The WebLogic domain must be installed into the folder that will be mounted as `/shared/domain`. The recommended approach is to use the provided `create-weblogic-domain.sh` script; however, instructions are also provided for manually installing and configuring a WebLogic domain (see [Manually creating a domain](manually-creating-domain.md)).

site/v1.0/database.md

@@ -1,3 +1,5 @@
+> **WARNING** This documentation is for version 1.0 of the operator.  To view documenation for the current release, [please click here](/site).
+
 # Running the Oracle Database in Kubernetes
 
 **PLEASE NOTE**:  This page is a work in progress.  We will update this with either better details about how to put the data files onto a persistent volume, or a pointer to the official Oracle Database Kubernetes pages, or both.