Reference

ClientIntents example (YAML)

apiVersion: k8s.otterize.com/v1alpha3
kind: ClientIntents
metadata:
  name: client-server-access
  namespace:  otterize-example
spec:
  service:
    # The name of the service initiating the connection
    name: client
  calls:
    # The name of the service receiving the connection. Multiple names can be provided
    - name: server
    # multiple services can be added
    - name: orderservice
      # Optional granular rules can be added like the HTTPResources options below.
      type: http
      HTTPResources:
        - path: /orders/*
          methods: [ get, post ]

ClientIntents and DNS values

When a ClientIntent is specified utilizing DNS identifiers, such as domain names, it initiates a sequence of operations to integrate the relevant IP addresses into the respective NetworkPolicies.

1. The Network Mapper incorporates a DNS cache layer, which identifies and archives all resolved DNS records alongside their corresponding IPv4 and IPv6 IP addresses.
2. Without a ClientIntent associated with the given domain or its related IP addresses, Otterize will propose a policy tailored to the observed traffic.
3. Upon the application of a ClientIntent with a domain name present in the cache, the NetworkMapper dynamically updates the intent’s status section at one-second intervals with any newly identified IP addresses. It is important to note that Otterize retains all previously identified IP addresses to ensure backward compatibility.
4. The Intents Operator reviews changes within the status section and amends the associated NetworkPolicy to include these newly discovered IP addresses.

Helm Chart options

Key	Description	Default
global.deployment.networkMapper	Whether or not to deploy network-mapper.	true

View the Helm chart reference for all other options

Network mapper parameters

All configurable parameters of the network mapper can be configured under the alias networkMapper. Further information about network mapper parameters can be found in the network mapper's chart.

CLI: Network mapper commands

All otterize network-mapper commands share a set of optional flags which will not be repeated in the documentation for each command.

otterize network-mapper reset

Resets the network mapper by deleting all map information built up so far in memory.

---

otterize network-mapper list [-n <namespace1>,<namespace2>,...]

Return the network map built by the network mapper since it started, or since it was reset, as a list of clients and the servers they call.

Options

Name	Default	Description
-n or --namespaces		Include only clients in these namespaces (comma-separated).

Returns

Here's a partial output from otterize network-mapper list -n otterize-ecom-demo:

cartservice in namespace otterize-ecom-demo calls:
  - redis-cart
checkoutservice in namespace otterize-ecom-demo calls:
  - cartservice
  - currencyservice
  - emailservice
  - paymentservice
  - productcatalogservice
  - shippingservice
frontend in namespace otterize-ecom-demo calls:
  - adservice
  - cartservice
  - checkoutservice
  - currencyservice
  - productcatalogservice
  - recommendationservice
  - shippingservice
loadgenerator in namespace otterize-ecom-demo calls:
  - frontend
recommendationservice in namespace otterize-ecom-demo calls:
  - productcatalogservice

---

otterize network-mapper visualize [--format=png | --format=jpg] [-n <namespace1>,<namespace2>,...] -o <path> Return the network map built by the network mapper since it started, or since it was reset, as an image.

Uses GraphViz (specifically go-graphviz) to generate the image.

Options

Name	Default	Description
--format	png	Image output format: "png" or "jpg".
-n or --namespaces		Include only clients in these namespaces (comma-separated).
-o or --output-path		Filename for the image.
--exclude-labels		A list of labels that would exclude services from list/export. example: "include=false"
--exclude-services		A list of service to exclude from list/export. example: "service1,service2"

Returns

Here's the image generated by running otterize network-mapper visualize -n otterize-ecom-demo -o otterize-ecom-demo.png:

---

otterize network-mapper export [--format] [-n <namespace1>,<namespace2>,...] [-o <path>] [--output-type <output-type>]

Return the network map built by the network mapper since it started, or since it was reset, as YAML client intents file(s) or as JSON file(s).

Options

Name	Default	Description
--format	yaml	Specifies the format for the export: either yaml or json.
-n or --namespaces		Export only clients in these namespaces (comma-separated).
-o or --output	STDOUT	Filename or directory for redirecting the output.
--output-type	single-file	Whether the output should be written as a single file (single-file) or as multiple files in a directory (dir). Requires the -o or --output to point to a directory.
--server		Export only intents for clients that call this server. The server name must be specified with both service name and namespace, in the format <SERVERNAME>.<SERVER_NAMESPACE>. Example: cartservice.otterize-ecom-demo.
--exclude-labels		A list of labels that would exclude services from list/export. Example: include=false would exclude any service labeled with include=false from being included in list/export.
--exclude-services		A list of services to exclude from list/export. Example: service1,service2.

Returns

Here's a partial output from otterize network-mapper export -n otterize-ecom-demo:

apiVersion: k8s.otterize.com/v1alpha3
kind: ClientIntents
metadata:
  name: cartservice
  namespace: otterize-ecom-demo
spec:
  service:
    name: cartservice
  calls:
    - name: redis-cart
      type: http
---
apiVersion: k8s.otterize.com/v1alpha3
kind: ClientIntents
metadata:
  name: checkoutservice
  namespace: otterize-ecom-demo
spec:
  service:
    name: checkoutservice
  calls:
    - name: cartservice
      type: http
    - name: currencyservice
      type: http