Enterprise-app CF to K8s migration and tutorial enhancement for ease of use by users new to Move2Kube, Docker & Kubernetes.

[Akash-Nayak]

This issue can be used to keep track of points which can be used for updating the tutorials and Move2Kube to enhance the user experience of using Move2Kube.

• Registry namespace question causes confusion between Docker registry namespace and Kubernetes cluster namespace.
• Where can the user find the target registry namespace? For quay -> Username in quay to be used (can be mentioned about it in the tutorial to make it clear? The hint in the question can be elaborated to make it clear)
• Update the tutorial corresponding to latest Move2Kube release.
• Currently in the tutorial the instructions are for deployment to Minikube cluster, which might be slightly different for deployment to OpenShift/K8s cluster. Should we include some additional sections/instructions to show how to deploy to K8s/OpenShift cluster? For example, the ingress host domain answer will differ from what we enter for minikube.
• Where to find the ingress host domain, a Cloud Foundry user new to Kubernetes might not know where to find the ingress host domain.
• If user is using quay.io for pushing images, the repository's visibility needs to be made public in quay by the user. Some instruction related to that can be included in the tutorial.
• Should the Move2Kube version to be used for the tutorial be freezed while updating the tutorial? Because, the latest Move2Kube version might not be in sync with the tutorial which could create some confusion.
• If yes for above question, then include Move2Kube installation command in the tutorial to install the specific version.
• The m2kconfig file which can be used by the user should also be kept up-to-date.
• Also, the current m2kconfig file already contains the answers for cluster type, docker registry, registry namespace, ingress host domain. So, the config file cannot be used for actual K8s/OCP deployment. Should we remove these questions, so that users can enter the answers themselves.
• The default answer for URL/Path for the frontend service is /frontend, but it doesn't work. So, in the tutorial it needs to be clearly mentioned that the leading / should be dropped and frontendcan be entered as the answer, so that it gets used as the subdomain and the URL/Route remains unique (frontend.<ingress_host_domain>).
• Update the tutorial, remove irrelevant things like the config-utils folder getting detected as a spurious service which no more exists in the enterprise-app.