[
https://issues.apache.org/jira/browse/IGNITE-10051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reassigned IGNITE-10051:
------------------------------------
Assignee: Akmal Chaudhri
> Kubernetes documentation improvements
> -------------------------------------
>
> Key: IGNITE-10051
> URL: https://issues.apache.org/jira/browse/IGNITE-10051
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Affects Versions: 2.6
> Reporter: Maxim Pudov
> Assignee: Akmal Chaudhri
> Priority: Major
> Fix For: 2.8
>
> Attachments: kube-dashboard-access.yaml, mongodb-deployment.yaml
>
>
> I verified the deployment instructions of a kubernetes cluster with apache
> ignite and found some issues.
> 1. AWS deployment:
> [https://apacheignite.readme.io/docs/amazon-web-services-eks-deployment]
> miss print:
> {quote}{{kubbectl get pods}}
> {quote}
> has to be:
> {quote}{{kubectl get pods}}
> {quote}
> 2. Google Cloud deployment
> [https://apacheignite.readme.io/docs/google-cloud-deployment]
> Screenshots seem to be outdated
> 3. Microsoft Azure deployment
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment#section-access-to-your-kubernetes-cluster]
> 3.1 At first I had no access to Kubernetes dashboard having this error:
> azure kubernetes dashboard namespaces is forbidden: User
> "system:serviceaccount:kube-system:kubernetes-dashboard" cannot list
> namespaces at the cluster scope
> This problem was solved by adding this config:
> {quote}kubectl create -f [^kube-dashboard-access.yaml]
> {quote}
> 3.2 Screenshots seem to be outdated for azure too.
> 4. Stateless deployment:
> [https://apacheignite.readme.io/docs/stateless-deployment]
> 4.1 At first we create example-cube-rbac.xml locally, but then we don't use
> it.
> 4.2 Instead the configuration file ignite-deployment.yaml
> ([https://apacheignite.readme.io/docs/stateless-deployment#section-ignite-pods-deployment])
> points to the wrong external configuration file:
> {quote}{{https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-persistence.xml}}
> {quote}
> I believe, it has to point to
> {quote}[{{https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-rback.xml}}|https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-rbac.xml]
> {quote}
> 4.3 In the same configuration file ignite-deployment.yaml there is a row
> {quote}{{serviceAccountName: ignite}}
> {quote}
> with Tab symbol, which has to be replaced with double Space.
> 5. Web console kubernetes installation.
> [https://apacheignite-tools.readme.io/docs/kubernetes-installation]
> 5.1 mongodb-deployment.yaml doesn't work as is. I had to modified it (check
> the attachment [^mongodb-deployment.yaml])
> 5.2 web-console-deployment.yaml - default image values aren't specified for
> frontend and backend (apacheignite/web-console-frontend,
> apacheignite/web-console-backend)
> 5.3 web-agent-deployment.yaml - serviceAccountName: "ignite-cluster" is
> incorrect. I guess "ignite" is the right one.
> 5.4 No such docker image as apacheignite/web-agent:mytag3.
> 6. General suggestions for kubernetes cluster deployment on GCC, AWS, Azure.
> 6.1 Create cluster via AWS Console, not command line. It's easier to pick
> values from drop down lists, and we don't provide complete installation via
> command line anyway.
> 6.2 When we suggest to use our configuration files for setting up services
> and pods, it is worth mentioning that our configs contain region parameter
> (zones: eu-west-1a) and user has to modify it himself.
> 6.3 The link to download configuration files points to the master branch,
> which could cause problems in future. For AWS it's
> [https://github.com/apache/ignite/tree/master/modules/kubernetes/config/eks]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
