Rename Clusters to Kubernetes
- This issue will continue to be product managed by @bikebilly
- UX will be done by @dimitrieh
- FE: @winh
- BE: At this point, no BE work is expected to be required.
- BE point of contact for technical help if it is required: @grzesiek first, and then @ayufan if @grzesiek is unavailable.
- Docs changes to be handled and/or reviewed by @axil
- Slack channel: #f_gke_integration
- A demo for this feature is targeted for Feb 23 or 24, 2018.
Description
Our Kubernetes integration is available under CI/CD > Clusters, but because of the generic term, users can miss that we are referring to a Kubernetes cluster used to deploy applications. Also, the previous integration service was called Kubernetes.
Since we are not considering any other cluster architecture than Kubernetes for the foreseeable future, we can consider if renaming Clusters in Kubernetes can improve the discoverability of the feature. Leveraging the Kubernetes name works well today, since it is having a lot of visibility and traction.
We all know what we mean when we are talking about clusters in GitLab, but our users may not.
Design/Implementation
Scope
All other references that were before cluster(s)
to Kubernetes cluster(s)
-
application
-
documentation
-
blog articles 10.5 and 10.5+
Contents
We need to consider every single occurence of the word, as we can say "Multiple Clusters" but not "Multiple Kubernetes", or "select a cluster" but not "select a Kubernetes".
Steps:
-
in the menu bar, use Kubernetes instead of Clusters -
in the page titles and breadcrumbs, view/page references, use Kubernetes instead of Clusters -
in the sentences, or docs, evaluate case by case what is more appropriate
- cluster -> Kubernetes
- cluster -> Kubernetes cluster
- clusters -> Kubernetes clusters