Merge branch 'master' into sishida_1397_remote

Author: micgibso

docs/_data/docstoc.yml

@@ -66,15 +66,15 @@
         - title: 'Installing Kibana and filtering logs in IBM Cloud Private'
           url: viewkibanalogs.html
 
-- title: 'Deploying Codewind remote'
+- title: 'Deploying Codewind remotely'
   children:
     - title: 'Overview'
       url: remoteoverview.html
-    - title: 'Configuring Codewind remote'
+    - title: 'Configuring your remote deployment of Codewind'
       url: remoteconfiguring.html
     - title: 'Entering remote connection settings'
       url: remoteconnectionui.html
-    - title: 'Removing Codewind remote'
+    - title: 'Removing your remote deployment of Codewind'
       url: remoteremoving.html
 
 - title: 'Performance monitoring'

docs/_data/newstoc.yml

@@ -1,3 +1,6 @@
+- title: 'Codewind 0.7.0'
+  url: news07.html
+
 - title: 'Codewind 0.6.0'
   url: news06.html
 

docs/_documentations/mdt-che-installinfo.md

@@ -28,7 +28,7 @@ Installing Codewind for Eclipse Che comprises the following steps:
    - Because Codewind uses RWX (ReadWriteMany) volumes to provide persistent storage, you need to use NFS for storage on OpenShift 4.
 2. Ensure that the cluster can pull images from `docker.io/eclipse` and `quay.io/eclipse`.
    - Both Eclipse Che and Eclipse Codewind host their Docker images at those locations. Ensure that your cluster can pull from that registry and does not have `ImagePullPolicies` blocking it from accessing Docker Hub.
-3. Set up the ClusterRole for Codewind. Run `kubectl apply -f https://raw.githubusercontent.com/eclipse/codewind-che-plugin/0.6.0/setup/install_che/codewind-clusterrole.yaml`
+3. Set up the ClusterRole for Codewind. Run `kubectl apply -f https://raw.githubusercontent.com/eclipse/codewind-che-plugin/0.7.0/setup/install_che/codewind-clusterrole.yaml`
 
 # Setting up Che
 
@@ -38,7 +38,7 @@ The fastest way to install Eclipse Che for use with Codewind is to use the `chec
 
 Complete the following steps after you install `chectl`:
 
-1. Download the [codewind-che checluster yaml](https://github.com/eclipse/codewind-che-plugin/blob/master/setup/install_che/che-operator/codewind-checluster.yaml) file to your machine.
+1. Download the [codewind-che checluster yaml](https://github.com/eclipse/codewind-che-plugin/blob/0.7.0/setup/install_che/che-operator/codewind-checluster.yaml) file to your machine.
     - You can modify this file, but leave the `spec.server.cheWorkspaceClusterRole` field set to `eclipse-codewind` and the `spec.storage.preCreateSubPaths` field set to `true`.
 2. If you're installing on a Kubernetes platform other than OpenShift, determine your Ingress domain. If you're unsure of your Ingress domain, ask your cluster administrator.
     - Set the `spec.server.ingressDomain` field in the Che `.yaml` to the Ingress domain.
@@ -51,7 +51,7 @@ Complete the following steps after you install `chectl`:
 If you already have an existing Che install, it's relatively easy to update it for Codewind.
 
 After creating the Codewind ClusterRole in the prerequisites step, run the following command, where `$NAMESPACE` is the namespace your Che workspaces run in (by default `che`):
-`kubectl apply -f https://raw.githubusercontent.com/eclipse/codewind-che-plugin/0.6.0/setup/install_che/codewind-rolebinding.yaml -n $NAMESPACE`
+`kubectl apply -f https://raw.githubusercontent.com/eclipse/codewind-che-plugin/0.7.0/setup/install_che/codewind-rolebinding.yaml -n $NAMESPACE`
 
 ### Enabling privileged and root containers to run
 
@@ -86,7 +86,7 @@ http://<che ingress domain>/f?url=<hosted devfile URL>
 
 Codewind includes a ready-to-use devfile with its plug-ins. Enter the following URL to create a workspace from the devfile:
 ```
-http://<che ingress domain>/f?url=https://raw.githubusercontent.com/eclipse/codewind-che-plugin/master/devfiles/0.6.0/devfile.yaml
+http://<che ingress domain>/f?url=https://raw.githubusercontent.com/eclipse/codewind-che-plugin/0.7.0/devfiles/0.7.0/devfile.yaml
 ```
 
 For other sample devfiles, see https://github.com/kabanero-io/codewind-templates/tree/master/devfiles.

docs/_documentations/remote-configuring.md

@@ -1,7 +1,7 @@
 ---
 layout: docs
-title: Configuring Codewind remote
-description: Configuring your environment to use Codewind remote
+title: Configuring your remote deployment of Codewind
+description: Configuring your environment to use your remote deployment of Codewind
 keywords: users, projects, Kubernetes, LDAP, user management, access management, login, deployment, pod, security, securing cloud connection
 duration: 5 minutes
 permalink: remoteconfiguring
@@ -10,9 +10,9 @@ parent: installoncloud
 order: 1
 ---
 
-# Configuring Codewind remote
+# Configuring your remote deployment of Codewind
 
-To use Codewind remote, configure your system by following these steps. 
+Configure your remote deployment of Codewind by following these steps. 
 
 ## Prerequisites
 - Install your preferred IDE on your local machine. For more information about installing Eclipse, see [Getting started with Codewind for Eclipse](mdteclipsegettingstarted.html), or for more information about installing VS Code, see [Getting started with Codewind for VS Code](mdt-vsc-getting-started.html).
@@ -21,7 +21,7 @@ To use Codewind remote, configure your system by following these steps.
 
 ## Procedure
 
-To securely configure Codewind remote there are two options, configuring Kubernetes for Docker Desktop, or configuring a cloud deployment that does not have an Ingress NGINX controller, for example, OpenShift. 
+To securely configure your remote deployment of Codewind, there are two options, configuring Kubernetes for Docker Desktop, or configuring a cloud deployment that does not have an Ingress NGINX controller, for example, OpenShift. 
 
 ### Configuring Kubernetes for Docker Desktop
 
@@ -39,7 +39,7 @@ To securely configure Codewind remote there are two options, configuring Kuberne
    - `export INGRESS_DOMAIN=$(kubectl get services --namespace ingress-nginx -o jsonpath='<.items[*].spec.clusterIP>')`
    - `sudo ifconfig lo0 alias $<INGRESS_DOMAIN>`
 
-3. Create the remote deployment by entering the following `cwctl` command: 
+3. Create the remote deployment of Codewind by entering the following `cwctl` command: 
 
    `cwctl install remote \`
      `--namespace <your_namespace>  \`
@@ -56,7 +56,7 @@ To securely configure Codewind remote there are two options, configuring Kuberne
 
 1. If you are deploying to a cloud that does not have an Ingress NGINX controller, for example, OpenShift, you must provide the ingress value in the `cwctl install remote \` command during installation. You can derive the `ingress` value from the cluster URL. To do this, go to the OpenShift console, for example, `https://<mycluster>|<myaddress>.nip.io:7443/console`, and then derive the `ingress` value, for example, from the previous address, this would be `apps.<mycluster>.<myaddress>.nip.io`. OpenShift also refer to this as the `routing-suffix`. 
 
-2. Create the remote deployment by issuing the following example `cwctl` command: 
+2. Create the remote deployment of Codewind by issuing the following example `cwctl` command: 
 
    `cwctl install remote \`
      `--namespace <your_namespace>  \`
@@ -70,6 +70,10 @@ To securely configure Codewind remote there are two options, configuring Kuberne
 
    Where `keycloakAdminUser` and `keycloakAdminPassword` are the Keycloak Administrator's user credentials, and `keycloakDevUser` and `keycloakDevUserPassword` are the credentials of the first user to use the service. 
 
+3. Codewind is required to run as privileged and as root because it builds container images. If your cluster is running OpenShift, run the following commands where `<namespace>` is the namespace into which you plan to install Codewind:
+- To enable privileged containers, enter `oc adm policy add-scc-to-group privileged system:serviceaccounts:<namespace>`.
+- To enable containers to run as root, enter `oc adm policy add-scc-to-group anyuid system:serviceaccounts:<namespace>`.
+
 ### Codewind CLI command explanation and sample output
 
 The `cwctl install remote` command:
@@ -84,7 +88,7 @@ The `cwctl install remote` command:
 
 You see example output similar to the following, this for a Linux/macOS deployment on Kubernetes:
 
-```
+```sh
 ~ cwctl --insecure install remote \
   --namespace codewind  \
   --kadminuser admin \

docs/_documentations/remote-overview.md

@@ -1,18 +1,18 @@
 ---
 layout: docs
-title: Deploying Codewind remote
-description: Deploying Codewind remote
-keywords: users, projects, Kubernetes, LDAP, user management, access management, login, deployment, pod, security, securing cloud connection
+title: Deploying Codewind remotely
+description: Deploying Codewind remotely
+keywords: users, projects, Kubernetes, LDAP, user management, access management, login, deployment, pod, security, securing cloud connection, remote deployment of Codewind
 duration: 5 minutes
 permalink: remoteoverview
 type: document
 parent: installoncloud
 order: 1
 ---
 
-# Deploying Codewind remote
+# Deploying Codewind remotely
 
-Codewind remote is where you develop your code locally and build and run it remotely and securely in the cloud. This option is incredibly useful because it frees up your local machine to focus purely on developing code and you use the cloud's resources to build and run your apps. Codewind enables you to develop your apps securely by securing the connection between your local editor and your remote cloud deployment. To do this, Codewind uses Keycloak, an open source identity and access management solution for modern applications and services which is highly configurable to your environment. 
+Deploying Codewind remotely enables you to develop your code locally and then build and run it remotely and securely in the cloud. This option is incredibly useful because it frees up local resource usage and you use the cloud's resources to build and run your apps. By using [Keycloak](https://www.keycloak.org/), the connection between your local editor and your remote cloud deployment is secure.
 
 You install your preferred IDE on your local machine. For more information about installing Eclipse, see [Getting started with Codewind for Eclipse](mdteclipsegettingstarted.html), or for more information about installing VS Code, see [Getting started with Codewind for VS Code](mdt-vsc-getting-started.html).
 
@@ -22,7 +22,7 @@ You then use the Codewind features inside your preferred IDE to create a connect
 
 Codewind enables you to choose which preferred IDE you want to use, however do not use two different IDEs at the same time. For the best user experience, choose which one you want to use, and disable the other. 
 
-To configure Codewind remote, see [Configuring Codewind remote](remoteconfiguring.html).
+To configure your remote deployment of Codewind, see [Configuring your remote deployment of Codewind](remoteconfiguring.html).
 
 ## Codewind remote security overview
 

docs/_documentations/remote-removing.md

@@ -1,7 +1,7 @@
 ---
 layout: docs
-title: Removing Codewind remote
-description: Removing Codewind remote
+title: Removing your remote deployment of Codewind
+description: Removing your remote deployment of Codewind
 keywords: users, projects, Kubernetes, LDAP, user management, access management, login, deployment, pod, security, securing cloud connection
 duration: 5 minutes
 permalink: remoteremoving
@@ -10,7 +10,31 @@ parent: installoncloud
 order: 1
 ---
 
-## Removing Codewind remote
+# Removing your remote deployment of Codewind
 
-To remove Codewind remote, enter the following `cwctl` command: `cwctl remove remote --namespace {mynamespace} --workspace {workspaceID}`
+The Codewind CLI `cwctl` is designed to do almost all the steps required to remove a remote deployment of Codewind by chaining together a number of Kubernetes operations.
 
+There are two modes of use. You can:
+1. Remove Codewind.
+2. Remove Keycloak. A Keycloak service can provide authentication services to many Codewind deployments in different namespaces, so only remove it when you are sure it is no longer used.
+
+## Removing a remote deployment of Codewind
+
+To remove a remote deployment of Codewind, enter the following `cwctl` command:
+
+`cwctl remove remote --namespace <namespace> --workspace <workspaceID>`
+
+Where the command parameters `<namespace>` and `<workspaceID>` are used to identify which Kubernetes resources to remove. If you are unsure of the `<workspaceID>`, you can find it as part of the ingress or route URL, for example:
+
+`https://codewind-gatekeeper-k412oms7.apps.mycluster.X.X.X.X.nip.io`
+`                            ^^^^^^^^`
+
+## Removing Keycloak
+
+WARNING: Removing Keycloak breaks all remote deployments of Codewind that are using it for authentication services. 
+
+If you are ready to remove Keycloak, use the following `cwctl` command:
+
+`cwctl remove keycloak  --namespace <namespace> --workspace <workspaceID>`
+
+Where the command parameters `<namespace>` and `<workspaceID>` are used to identify which Kubernetes resources to remove.

docs/_news/news07.md

@@ -0,0 +1,33 @@
+---
+layout: news
+title: New for Codewind 0.7.0
+description: New for Codewind 0.7.0
+keywords: news, new, updates, update, version, hybrid
+duration: 1 minute
+permalink: news07
+---
+
+## Codewind 0.7.0
+Monday 16 December 2019
+
+#### ✨ Remote Deploy with Codewind: Tech Preview ✨
+
+You can now develop your code locally and securely build and deploy your apps in the cloud! Why is this cool?
+- Free up local resources. 👏
+- It's secure! 🔐 We use [Keycloak](https://keycloak.org/) to secure the connection between your local editor and remote cloud deployment.
+
+Curious? [Learn more](remoteoverview.html)!
+
+#### New Features and Highlights for 0.7.0
+
+**OpenShift Do (odo)**
+- You can now easily import existing projects into Codewind and [use odo](https://github.com/eclipse/codewind/issues/1115) to build and deploy projects to your OpenShift or OKD cluster.
+- Introducing [support for Java template](https://github.com/eclipse/codewind/issues/450) and Java projects can build and deploy [once configured](//permalink to landing page).
+- You no longer have to create your [docker registry secret](https://github.com/eclipse/codewind/issues/665) in Codewind.
+
+
+
+#### List of Fixes
+- Changes to the Eclipse plugin for Spring Server [post-code generation stability for OpenAPI](https://github.com/eclipse/codewind/issues/1116)
+- Appsody binary updated from 0.5.0 to 0.5.2 in the codewind-appsody-extension
+- Other security fixes