Istio Discovery Guide

Search…
This guide provides a basic overview of how to configure Grey Matter Catalog to retrieve service information from an Istio mesh control plane.
Prerequisites
1.An existing Grey Matter deployment following our Install on Kubernetes guide.
2.An Istio deployment installed in the same Kubernetes cluster in the istio-system namespace, following one of the Istio Installation Guides.
3.​Istio's Bookinfo application deployed in the same Kubernetes cluster, but in a separate istio-services namespace. See below for more details on why a separate namespace is required and how to perform this custom installation.
4.​greymatter CLI set up to connect to Grey Matter Catalog.
Deploying Istio's Bookinfo application
This guide requires that Istio services be deployed in a separate Kubernetes namespace from the Grey Matter deployment. The namespace for the Bookinfo application will use Istio's automatic sidecar injection setting. Separating Istio and Grey Matter services into different namespaces will prevent namespace collisions.
The following commands should be substituted for the ones encountered in the Bookinfo instructions:
1
kubectl label namespace istio-services istio-injection=enabled
2
kubectl apply -f samples/bookinfo/platform/kube/bookinfo.yaml -n istio-services
Copied!
Overview
1.Configure a connection to the Istio control plane
2.Configure service entries for tracking instances in the Istio mesh
Steps
1. Configure a connection to the Istio control plane
Control plane connections are tracked in Catalog using mesh configuration objects. The following example is a simple configuration object that specifies the address to Istio's control plane service. Save the following in a mesh.json file:
1
{
2
  "mesh_id": "istio-mesh-example",
3
  "mesh_type": "istio",
4
  "name": "Istio Example Mesh",
5
  "sessions": {
6
    "default": {
7
      "url": "istiod.istio-system.svc:15010"
8
    }
9
  }
10
}
Copied!
Use the greymatter CLI to create the configuration object in Catalog:
1
greymatter create catalog-mesh < mesh.json
Copied!
After creating a configuration object, Catalog responds with a summary including a status of each configured control plane connection, a map of instance counts, and mesh summary metadata. Note that the session_statuses.default session is marked as "Pending".
1
{
2
  "mesh_id": "istio-mesh-example",
3
  "configuration": {
4
    "mesh_id": "istio-mesh-example",
5
    "mesh_type": "istio",
6
    "name": "Istio Example Mesh",
7
    "sessions": {
8
      "default": {
9
        "url": "istiod.istio-system.svc:15010"
10
      }
11
    },
12
    "labels": {},
13
    "external_links": []
14
  },
15
  "session_statuses": {
16
    "default": "Pending"
17
  },
18
  "instance_counts": {},
19
  "metadata": {
20
    "owners": [],
21
    "capabilities": [],
22
    "service_count": 0,
23
    "service_stable_count": 0,
24
    "service_warning_count": 0,
25
    "service_down_count": 0,
26
    "instance_count": 0
27
  }
28
}
Copied!
To retrieve an updated status on the control plane connection, run:
1
greymatter get catalog-mesh istio-mesh-example
Copied!
If Catalog was able to connect to the Istio control plane, the mesh summary response should resemble the following:
1
{
2
  "mesh_id": "istio-mesh-example",
3
  "configuration": {
4
    "mesh_id": "istio-mesh-example",
5
    "mesh_type": "istio",
6
    "name": "Istio Example Mesh",
7
    "sessions": {
8
      "default": {
9
        "url": "istiod.istio-system.svc:15010"
10
      }
11
    },
12
    "labels": {},
13
    "external_links": []
14
  },
15
  "session_statuses": {
16
    "default": "OK"
17
  },
18
  "instance_counts": {
19
    "details-v1:9080": 1,
20
    "istio-egressgateway:15443": 1,
21
    "istio-egressgateway:8080": 1,
22
    "istio-egressgateway:8443": 1,
23
    "istio-ingressgateway:15021": 1,
24
    "istio-ingressgateway:15443": 1,
25
    "istio-ingressgateway:31400": 1,
26
    "istio-ingressgateway:8080": 1,
27
    "istio-ingressgateway:8443": 1,
28
    "productpage-v1:9080": 1,
29
    "ratings-v1:9080": 1,
30
    "reviews-v1:9080": 1,
31
    "reviews-v2:9080": 1,
32
    "reviews-v3:9080": 1
33
  },
34
  "metadata": {
35
    "owners": [],
36
    "capabilities": [],
37
    "service_count": 0,
38
    "service_stable_count": 0,
39
    "service_warning_count": 0,
40
    "service_down_count": 0,
41
    "instance_count": 0
42
  }
43
}
Copied!
The instance_counts field should be populated by host:port pairs each with their own instance count, indicating that Catalog was able to discover a number of instances (i.e. Kubernetes pods) for the service.
Each host:port pair refers to an individual Kubernetes deployment. If you want to organize this collection by Kubernetes service instead, run the following command to edit the istio-mesh-example configuration (ensure your $EDITOR environment variable is set):
1
greymatter edit catalog-mesh istio-mesh-example
Copied!
Edit the configuration so that labels has the following:
1
{
2
  ...
3
  "labels": {
4
    "group_by_k8s_service": "true" // note this is a string label
5
  }
6
}
Copied!
The greymatter CLI should respond with another "Pending" status for the default session. To retrieve the updated state of the mesh object from Catalog, run:
1
greymatter get catalog-mesh istio-mesh-example
Copied!
You should see the following under instance_counts. Note that the reviews:9080 Kubernetes service has 3 instances, whereas the previous setting showed 3 distinct Kubernetes deployments (i.e. reviews-v1:9080, reviews-v2:9080, and reviews-v3:9080).
1
{
2
  ...
3
  "instance_counts": {
4
    "details:9080": 1,
5
    "istio-egressgateway:15443": 1,
6
    "istio-egressgateway:8080": 1,
7
    "istio-egressgateway:8443": 1,
8
    "istio-ingressgateway:15021": 1,
9
    "istio-ingressgateway:15443": 1,
10
    "istio-ingressgateway:31400": 1,
11
    "istio-ingressgateway:8080": 1,
12
    "istio-ingressgateway:8443": 1,
13
    "productpage:9080": 1,
14
    "ratings:9080": 1,
15
    "reviews:9080": 3
16
  },
17
  ...
18
}
Copied!
2. Configure service entries for tracking instances in the Istio mesh
Services are tracked in Catalog using service configuration objects that reference mesh configuration objects. The following example is a simple service object that references istio-mesh-example. Save the following in a reviews.json file:
1
{
2
  "mesh_id": "istio-mesh-example",
3
  "service_id": "reviews:9080",
4
  "name": "Reviews",
5
  "minInstances": 1,
6
  "maxInstances": 3
7
}
Copied!
Use the greymatter CLI to create the service configuration object in Catalog:
1
greymatter create catalog-service < reviews.json
Copied!
After creating a service configuration object, Catalog responds with a summary that includes the configuration, additional discovered data, and individual service instances. Note that each instance contains a metadata object that includes a k8s_namespace, k8s_deployment, and k8s_service for identifying which resource is being referenced in your Kubernetes cluster.
1
{
2
  "service_id": "reviews:9080",
3
  "mesh_id": "istio-mesh-example",
4
  "name": "Reviews",
5
  "version": "",
6
  "description": "",
7
  "owner": "",
8
  "owner_url": "",
9
  "api_endpoint": "",
10
  "api_spec_endpoint": "",
11
  "capability": "",
12
  "runtime": "GO",
13
  "documentation": "",
14
  "prometheus_job": "reviews:9080",
15
  "min_instances": 1,
16
  "max_instances": 3,
17
  "enable_instance_metrics": false,
18
  "enable_historical_metrics": false,
19
  "business_impact": "low",
20
  "external_links": [],
21
  "mesh_type": "istio",
22
  "localities": [],
23
  "instances": [
24
    {
25
      "instance_id": "5c4cf820faaff06eaa19243c4b322362",
26
      "session": "default",
27
      "locality": "",
28
      "metadata": {
29
        "health_status": 0,
30
        "health_status_desc": "UNKNOWN",
31
        "istio_cluster": "outbound|9080||reviews.istio-services.svc.cluster.local",
32
        "k8s_deployment": "reviews-v2",
33
        "k8s_namespace": "istio-services",
34
        "k8s_service": "reviews"
35
      }
36
    },
37
    {
38
      "instance_id": "a7fb0d4aa029abe189f93cf6b6d03ee3",
39
      "session": "default",
40
      "locality": "",
41
      "metadata": {
42
        "health_status": 0,
43
        "health_status_desc": "UNKNOWN",
44
        "istio_cluster": "outbound|9080||reviews.istio-services.svc.cluster.local",
45
        "k8s_deployment": "reviews-v1",
46
        "k8s_namespace": "istio-services",
47
        "k8s_service": "reviews"
48
      }
49
    },
50
    {
51
      "instance_id": "c0e09925989960827fca906707977f9a",
52
      "session": "default",
53
      "locality": "",
54
      "metadata": {
55
        "health_status": 0,
56
        "health_status_desc": "UNKNOWN",
57
        "istio_cluster": "outbound|9080||reviews.istio-services.svc.cluster.local",
58
        "k8s_deployment": "reviews-v3",
59
        "k8s_namespace": "istio-services",
60
        "k8s_service": "reviews"
61
      }
62
    }
63
  ],
64
  "metadata": {},
65
  "status": "stable"
66
}
Copied!
To retrieve the service summary object again, run the following:
1
greymatter get catalog-service reviews:9080 --catalog.mesh=istio-mesh-example
Copied!
Questions
Need help with your installation?
Create an account at Grey Matter Support to reach our team.
Guides - Previous
App Development Guide
Next - Usage
Application
Last modified 8mo ago
Export as PDF
Copy link
Contents
Prerequisites
Overview
Steps
1. Configure a connection to the Istio control plane
2. Configure service entries for tracking instances in the Istio mesh
Questions