Update features - istio component status (#451)

- re-order Feature sections alphabetically by removing weights
- shorten install link titles to avoid wrapping

Author: jshaughn

content/en/docs/Features/_index.md

@@ -1,8 +1,6 @@
 ---
 title: "Features"
-date: 2018-06-20T19:04:38+02:00
-draft: false
-weight: 2
 description: An overview of important Kiali features.
+weight: 2
 ---
 

content/en/docs/Features/configuration.md

@@ -1,6 +1,6 @@
 ---
 title: "Istio Configuration"
-weight: 7
+description: "Using Kiali to generate Istio mesh-wide configuration."
 ---
 
 Kiali is more than observability, it also helps you to configure, update and validate your Istio service mesh.

content/en/docs/Features/details.md

@@ -1,7 +1,6 @@
 ---
 title: Detail Views
 description: Kiali provides list and detail views for your mesh components.
-weight: 3
 ---
 
 Kiali provides filtered list views of all your service mesh definitions. Each view provides health, details, YAML definitions and links to help you visualize your mesh. There are list and detail views for:

content/en/docs/Features/health.md

@@ -1,6 +1,6 @@
 ---
 title: "Health"
-weight: 2
+description: "How Kiali reflects your Service Mesh Health."
 ---
 
 Kiali help users know whether their service mesh is healthy. This includes the health of the mesh infrastructure itself, and the deployed application services.
@@ -11,6 +11,8 @@ Users can quickly confirm the health of their infrastructure by looking at the K
 
 ![Masthead Health](/images/documentation/features/health-masthead.png "Masthead Health")
 
+For more detail on how Kiali tracks the Istio infrastructure status, see the [Istio Status Feature]({{< relref "./istio-component-status" >}}).
+
 ## Overview Health
 
 The default Kiali page is an Overview Dashboard.  This view will quickly allow you to identify namespaces with issues.  It provides a summary of configuration health, component health and request traffic health.  The component health is selectable via a dropdown and the page offers various filter, sort and presentation options:

content/en/docs/Features/istio-component-status.md

@@ -1,38 +1,35 @@
 ---
-title: "Istio Status"
-date: 2018-06-20T19:04:38+02:00
-draft: false
-weight: 9
+title: "Istio Component Status"
+linkTitle: "Istio Status"
+description: "How Kiali monitors your Istio infrastructure."
 ---
 
-## Istio Component Status
+A service mesh simplifies application services by deferring the non-business logic to the mesh. But for healthy applications the service mesh infrastructure must also be running normally.  Kiali monitors the multiple components that make up the service mesh, letting you know if there is an underlying problem.
 
-The Istio service mesh architecture is comprised of several components, from istiod to Jaeger. Each component must work as expected for the mesh to work well overall. Kiali regularly checks the status of each Istio component to ensure the mesh is healthy.
+![Istio component status](/images/documentation/features/istio-status-masthead.png "Istio component status")
 
-![Istio components status: components not healthy or found](/images/documentation/features/istio-components-1.24.png "Istio components status: components not healthy or found")
+A component *status* will be one of: `Not found`, `Not ready`, `Unreachable`, `Not healthy` and `Healthy`. `Not found` means that Kiali is not able to find the deployment. `Not ready` means no pods are running.  `Unreachable` means that Kiali hasn't been successfully able to communicate with the component (Prometheus, Grafana and Jaeger). `Not healthy` means that the deployment doesn't have the desired amount of replicas running. Otherwise, the component is `Healthy` and it won't be shown in the list.
 
-A component *status* will be one of: `Not found`, `Unreachable`, `Not healthy` and `Healthy`. The `Not found` status means that Kiali is not able to find the deployment. The `Unreachable` status means that Kiali hasn't been succesfuly able to communicate with the component (Prometheus, Grafana and Jaeger). The `Not healthy` status means that the deployment doesn't have the desired amount of replicas running. The `Healthy` status is when the component is not in the previous ones, plus, healthy components won't be shown in the list.
+Regarding the *severity* of each component, there are only two options: `core` or `add-on`. The `core` components are those shown as errors (in red) whereas the `add-ons` are displayed as warnings (in orange).
 
-Regarding the *severity* of each component, there are only to options: `core` or `add-on`. The `core` components are those shown as errors (in red) whereas the `add-ons` are displayed as warnings (in orange).
+By default, Kiali checks that the `core` components "istiod", "ingress", and "egress" are installed and running in the control plane namespace, and that the `add-ons` "prometheus", "grafana" and "jaeger" are available.
 
-By default, Kiali checks the following components installed in the control plane namespace: istiod, ingress, egress; and prometheus, grafana and jaeger accessible thought their services.
+## Certificate Information Indicators
 
-## Certificates Information Indicators
+In some situations, it is useful to get information about the certificates used by internal mTLS, for example:
 
-In some situations, it would be useful to get information about the certificates used by internal mTLS, for example:
-
-* Know whether the default CA is used or if there is another CA configured
-* Check the certificates issuer and their validity timestamps to troubleshoot any issue with certificates
+* Know whether the default CA is used or if there is another CA configured.
+* Check the certificates issuer and their validity timestamps to troubleshoot any issue with certificates.
 
 The certificates shown depends on how Istio is configured. The following cases are possible:
 
-* Using Istio CA certificates (default), the information shown is from a secret named *istio-ca-secret*
-* Using https://istio.io/latest/docs/tasks/security/cert-management/plugin-ca-cert/[Plug in CA certificates, window=_blank], the information shown is from a secret named *cacerts*
-* Using https://istio.io/latest/docs/tasks/security/cert-management/dns-cert/[DNS certificates, window=_blank], the information shown is from reading many secrets found in Istio configuration
+* Using Istio CA certificates (default), the information shown is from a secret named *istio-ca-secret*.
+* Using [Plug in CA certificates](https://istio.io/latest/docs/tasks/security/cert-management/plugin-ca-cert/), the information shown is from a secret named *cacerts*.
+* Using [DNS certificates](https://istio.io/latest/docs/tasks/security/cert-management/dns-cert/), the information shown is from reading many secrets found in Istio configuration.
 
 The following is an example of viewing the default case:
 
-![Certificates information](/images/documentation/features/certificates-information-indicators.png "Certificates information")
+![Certificates information](/images/documentation/features/istio-status-certificate-info-indicators.png "Certificates information")
 
 Note that displaying this configuration requires permissions to read secrets (*istio-ca-secret* by default, possibly *cacerts* or any secret configured when using DNS certificates).
 

content/en/docs/Features/multi-cluster.md

@@ -1,8 +1,6 @@
 ---
-title: "Advanced Mesh Deployment and Multi-cluster support"
-date: 2018-06-20T19:04:38+02:00
-draft: false
-weight: 10
+title: "Multi-cluster Deployment"
+description: "Advanced Mesh Deployment and Multi-cluster support."
 ---
 
 A basic Istio mesh deployment has a single control plane with a single data plane, deployed on a single Kubernetes cluster. But Istio supports a variety of advanced 

content/en/docs/Features/security.md

@@ -1,8 +1,5 @@
 ---
 title: "Security"
-date: 2018-06-20T19:04:38+02:00
-draft: false
-weight: 8
 ---
 
 Kiali gives support to better understand how mTLS is used in Istio meshes. Find those helpers in the graph, the masthead menu, the overview page and specific validations.

content/en/docs/Features/topology.md

@@ -1,7 +1,6 @@
 ---
 title: Topology
 description: How Kiali visualizes the mesh topology.
-weight: 1
 ---
 
 Kiali offers multiple ways for users to examine their mesh Topology.  Each combines several information types to help users quickly evaluate the health of their service architecture.

content/en/docs/Features/tracing.md

@@ -1,7 +1,6 @@
 ---
 title: Tracing
 description: How Kiali integrates Distributed Tracing with Jaeger.
-weight: 4
 ---
 
 Kiali offers a native integration with Jaeger for Distributed Tracing.  As such, users can access Jaeger's trace visualizations.  But more

content/en/docs/Features/validations.md

@@ -1,6 +1,5 @@
 ---
 title: "Validation"
-weight: 5
 ---
 
 Kiali performs a set of validations on your Istio Objects, such as Destination Rules, Service Entries, and Virtual Services. Kiali's validations go above and beyond what Istio offers.  Where Istio offers mainly static checks for well-formed definitions, Kiali performs semantic validations to ensure that the definitions make sense, across objects, and in some cases even across namespaces.  Kiali validations are based on the runtime status of your service mesh.

content/en/docs/Features/wizards.md

@@ -1,8 +1,5 @@
 ---
 title: "Wizards"
-date: 2018-06-20T19:04:38+02:00
-draft: false
-weight: 6
 ---
 
 Kiali is more than observability, it also helps you to configure, update and validate your Istio service mesh.

content/en/docs/Installation/installation-guide/accessing-kiali.md

@@ -1,7 +1,6 @@
 ---
-title: "Accessing and exposing Kiali"
-date: 2021-09-12T00:00:00+00:00
-draft: false
+title: "Accessing Kiali"
+description: "Accessing and exposing Kiali"
 weight: 50
 ---
 

content/en/docs/Installation/installation-guide/advanced-install-options.md

@@ -1,7 +1,6 @@
 ---
-title: "Advanced installation options"
-date: 2021-09-12T00:00:00+00:00
-draft: false
+title: "Advanced Install"
+description: "Advanced installation options"
 weight: 60
 ---
 

content/en/docs/Installation/installation-guide/creating-updating-kiali-cr.md

@@ -1,7 +1,6 @@
 ---
-title: "Creating and updating the Kiali CR"
-date: 2021-09-12T00:00:00+00:00
-draft: false
+title: "The Kiali CR"
+description: "Creating and updating the Kiali CR"
 weight: 40
 ---
 

content/en/docs/Installation/installation-guide/example-install.md

@@ -1,7 +1,5 @@
 ---
-title: "Example Installation"
-date: 2021-10-20:00:00+00:00
-draft: false
+title: "Example Install"
 weight: 70
 ---
 

content/en/docs/Installation/installation-guide/install-with-helm.md

@@ -1,7 +1,5 @@
 ---
-title: "Installation via Helm"
-date: 2021-09-12T00:00:00+00:00
-draft: false
+title: "Install via Helm"
 weight: 20
 ---
 

content/en/docs/Installation/installation-guide/installing-with-operatorhub.md

@@ -1,7 +1,5 @@
 ---
-title: "Installation via OperatorHub"
-date: 2021-09-12T00:00:00+00:00
-draft: false
+title: "Install via OperatorHub"
 weight: 30
 ---