[jira] [Commented] (IGNITE-8923) Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)

["Denis Magda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576753#comment-16576753 ] 

Denis Magda commented on IGNITE-8923:
-------------------------------------

Looks good, thanks.

> Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
> --------------------------------------------------------------------
>
>                 Key: IGNITE-8923
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8923
>             Project: Ignite
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Roman Guseinov
>            Assignee: Denis Magda
>            Priority: Major
>             Fix For: 2.7
>
>         Attachments: config.zip, example-kube.xml, google_cloud_engine_deployment.zip, yaml.zip
>
>
> We have such documentation for Microsoft Azure [https://apacheignite.readme.io/docs/microsoft-azure-deployment]
> It would be great to publish the same for GCE.
> Here are steps which I used to deploy cluster (stateless, stateful) and web console:
> {code:java}
> ## Start Ignite Cluster
> 1. Grant cluster-admin role to current google user (to allow create roles):
> $ kubectl create clusterrolebinding myname2-cluster-admin-binding \
> --clusterrole=cluster-admin \
> --user=<email>
> 2. Create service account and grant permissions:
> $ kubectl create -f sa.yaml
> $ kubectl create -f role.yaml
> $ kubectl create -f rolebind.yaml
> 3. Create a grid service:
> $ kubectl create -f service.yaml
> 4. Deploy Ignite Cluster:
> $ kubectl create -f grid.yaml
> ## Enable Ignite Persistence
> 5. Deploy Ignite StatefulSet with enabled Persistence (instead of step 4).
> $ kubectl create -f grid-pds.yaml
> 6. Connect to the Ignite node and activate cluster:
> $ kubectl exec -it ignite-cluster-0 -- /bin/bash
> $ cd /opt/ignite/apache-ignite-*
> $ ./bin/control.sh --activate
> ## Deploy Web Console:
> 7. Create a volume to keep web console data:
> $ kubectl create -f console-volume.yaml
> 8. Create load balancer to expose HTTP port and make web console available by service DNS-name (web-console.default.svc.cluster.local) inside Kuberntes enviroment:
> $ kubectl create -f console-service.yaml
> 9. Deploy Web Console:
> $ kubectl create -f console.yaml
> 10. Check external IP:
> $ kubectl get service web-console
> 11. Open Web Console in a web browser and Sign Up.
> 12. Move to User Profile page (Settings > Profile) and copy security token.
> 13. Insert security token into web-agent.yaml (TOKENS environment variable).
> 14. Deploy Web Agent:
> $ kubectl create -f web-agent.yaml
> {code}
> YAML and configs are attached.
> Creating a public Docker-image for Web Agent in progress: https://issues.apache.org/jira/browse/IGNITE-8526



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)