Add markdown lint github action + fix lint issues

.github/workflows/golangci-lint.yml → .github/workflows/lint.yml

@@ -1,4 +1,4 @@
-name: golangci-lint
+name: lint
 on:
   pull_request:
     types:
@@ -11,9 +11,10 @@ permissions:
   contents: read
   # Optional: allow read access to pull request. Use with `only-new-issues` option.
   # pull-requests: read
+
 jobs:
   golangci:
-    name: lint
+    name: golangci-lint
     runs-on: ubuntu-20.04
     steps:
       - uses: actions/setup-go@v3
@@ -54,3 +55,14 @@ jobs:
 
           # Optional: if set to true then the action don't cache or restore ~/.cache/go-build.
 #          skip-build-cache: true
+
+  markdownlint:
+    name: Check for Markdown errors
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+      - uses: articulate/actions-markdownlint@v1
+        with:
+          config: .markdownlint.json
+          files: '**/*.md'

.markdownlint.json

@@ -0,0 +1,5 @@
+{
+  "default": true,
+  "MD013": false,
+  "MD033": false
+}

CODE_OF_CONDUCT.md

@@ -55,7 +55,7 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at help@otterize.com. All
+reported by contacting the project team at <help@otterize.com>. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.
@@ -68,9 +68,9 @@ members of the project's leadership.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
 
 [homepage]: https://www.contributor-covenant.org
 
 For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+<https://www.contributor-covenant.org/faq>

README.md

@@ -1,7 +1,6 @@
 # Otterize network mapper
 
-<img title="Otter Manning Helm" src="./otterhelm.png" width=200 />
-
+<img title="Otter Manning Helm" src="./otterhelm.png" width=200 alt="logo" />
 
 ![build](https://github.com/otterize/network-mapper/actions/workflows/build.yaml/badge.svg)
 [![Go Report Card](https://goreportcard.com/badge/github.com/otterize/network-mapper/src)](https://goreportcard.com/report/github.com/otterize/network-mapper/src)
@@ -20,11 +19,10 @@ Maps pod-to-pod traffic, pod-to-Internet traffic, and even AWS IAM traffic, with
 * [Contributing](#contributing)
 * [Slack](#slack)
 
-
-https://user-images.githubusercontent.com/20886410/205926414-a5fb6755-b5fa-45f3-9b15-d4f867547836.mp4
-
+<https://user-images.githubusercontent.com/20886410/205926414-a5fb6755-b5fa-45f3-9b15-d4f867547836.mp4>
 
 ## About
+
 The Otterize network mapper is a zero-config tool that aims to be lightweight and doesn't require you to adapt anything in your cluster. Its goal is to give you insights about traffic in your cluster without a complete overhaul or the need to adapt anything to it, unlike other solutions, which may require deploying a new CNI, a service mesh, and so on.
 
 You can use the [Otterize CLI](https://github.com/otterize/otterize-cli) to list the traffic by client, visualize the traffic, export the results as JSON or YAML, or reset the traffic the mapper remembers.
@@ -35,8 +33,8 @@ Example output after running `otterize network-mapper visualize` on the [Google
 The same microservices demo in the [Otterize Cloud](https://otterize.com/cloud-beta) access graph, as it appears when you choose to connect the network mapper to Otterize Cloud:
 ![image](cloud-example.png)
 
-
 Example output after running `otterize network-mapper list` on the Google Cloud microservices demo:
+
 ```bash
 cartservice in namespace otterize-ecom-demo calls:
   - redis-cart
@@ -60,99 +58,124 @@ loadgenerator in namespace otterize-ecom-demo calls:
 recommendationservice in namespace otterize-ecom-demo calls:
   - productcatalogservice
 ```
- 
+
 ## Try the network mapper
 
 Try the [quickstart](https://docs.otterize.com/quick-tutorials/k8s-network-mapper) to get a hands-on experience in 5 minutes.
 
 Looking to map AWS traffic? Check out the [AWS visibility tutorial](https://docs.otterize.com/features/aws-iam/tutorials/aws-visibility).
 
 ## Installation instructions
+
 ### Install and run the network mapper using Helm
+
 ```bash
 helm repo add otterize https://helm.otterize.com
 helm repo update
 helm install network-mapper otterize/network-mapper -n otterize-system --create-namespace --wait
 ```
+
 ### Install Otterize CLI to query data from the network mapper
+
 Mac
+
 ```bash
 brew install otterize/otterize/otterize-cli
 ```
+
 Linux 64-bit
+
 ```bash
 wget https://get.otterize.com/otterize-cli/v1.0.5/otterize_linux_x86_64.tar.gz
 tar xf otterize_linux_x86_64.tar.gz
 sudo cp otterize /usr/local/bin
 ```
+
 Windows
+
 ```bash
 scoop bucket add otterize-cli https://github.com/otterize/scoop-otterize-cli
 scoop update
 scoop install otterize-cli
 ```
+
 For more platforms, see [the installation guide](https://docs.otterize.com/installation#install-the-otterize-cli).
 
 ### Components
-- Mapper - the mapper is deployed once per cluster, and receives traffic information from the sniffer and watchers, and resolves the information to communications between [service identities](https://docs.otterize.com/reference/service-identities).
-- Sniffer - the sniffer is deployed to each node using a DaemonSet, and is responsible for capturing node-local DNS traffic and inspecting open connections.
-- Kafka watcher - the Kafka watcher is deployed once per cluster and is responsible for detecting accesses to Kafka topics, which services perform those accesses and which operations they use.
-- Istio watcher - the Istio watcher is part of the Mapper and queries Istio Envoy sidecars for HTTP traffic statistics, which are used to detect HTTP traffic with paths. Currently, the Istio watcher has a limitation where it reports all HTTP traffic seen by the sidecar since it was started, regardless of when it was seen.
-- AWS IAM visibility - The AWS IAM visibility components are optionally deployed with `--set aws.visibility.enabled=true`. Label pods with `network-mapper.otterize.com/aws-visibility: true`, and if connected to Otterize Cloud, the Cloud will combine the information to put together a map of accesses to AWS resources, which you can export as ClientIntents yamls for use with the (Intents Operator)[https://github.com/otterize/intents-operator].
+
+* Mapper - the mapper is deployed once per cluster, and receives traffic information from the sniffer and watchers, and resolves the information to communications between [service identities](https://docs.otterize.com/reference/service-identities).
+* Sniffer - the sniffer is deployed to each node using a DaemonSet, and is responsible for capturing node-local DNS traffic and inspecting open connections.
+* Kafka watcher - the Kafka watcher is deployed once per cluster and is responsible for detecting accesses to Kafka topics, which services perform those accesses and which operations they use.
+* Istio watcher - the Istio watcher is part of the Mapper and queries Istio Envoy sidecars for HTTP traffic statistics, which are used to detect HTTP traffic with paths. Currently, the Istio watcher has a limitation where it reports all HTTP traffic seen by the sidecar since it was started, regardless of when it was seen.
+* AWS IAM visibility - The AWS IAM visibility components are optionally deployed with `--set aws.visibility.enabled=true`. Label pods with `network-mapper.otterize.com/aws-visibility: true`, and if connected to Otterize Cloud, the Cloud will combine the information to put together a map of accesses to AWS resources, which you can export as ClientIntents yamls for use with the [Intents Operator](https://github.com/otterize/intents-operator).
 
 ### DNS responses
+
 DNS is a common network protocol used for service discovery. When a pod (`checkoutservice`) tries to connect to a Kubernetes service
 (`orderservice`) or another pod, a DNS query is sent out. The network mapper watches DNS responses and extracts the IP addresses, which are used for the [service identity resolving process](https://docs.otterize.com/reference/service-identities).
 
 ### Active TCP connections
+
 DNS responses will only appear when new connections are opened. To handle long-lived connections, the network mapper also queries open TCP connections in a manner similar to `netstat` or `ss`. The IP addresses are used for the [service identity resolving process](https://docs.otterize.com/reference/service-identities), as above.
 
 ### Kafka logs
+
 The Kafka watcher periodically examines logs of Kafka servers provided by the user through configuration, parses them and deduces topic-level access to Kafka from pods in the cluster.
 The watcher is only able to parse Kafka logs when Kafka servers' Authorizer logger is configured to output logs to `stdout` with `DEBUG` level.
 
 ### Istio sidecar metrics
+
 The Istio watcher, part of the Network mapper periodically queries for all pods with the `security.istio.io/tlsMode` label, queries each pod's Istio sidecar for metrics about connections, and deduces connections with HTTP paths between pods covered by the Istio service mesh.
 
 ### AWS IAM visibility
+
 AWS IAM visibility consists of several components: a HTTP proxy that proxies AWS traffic for pods which you opt-in on using the label `network-mapper.otterize.com/aws-visibility: true`, a webhook admission controller that patches Pods with that label as they are admitted to add a certificate for the HTTP proxy and direct DNS traffic for amazonaws.com to a DNS server belonging to the network mapper, and finally said DNS server which responds only to amazonaws.com requests and forwards the rest to the cluster's DNS server.
 
 ### Service name resolution
+
 Service names are resolved in one of two ways:
+
 1. If an `otterize/service-name` label is present, that name is used.
 2. If not, a recursive look-up is performed for the Kubernetes resource owner for a pod until the root is reached.
-For example, if you have a `Deployment` named `client`, which then creates and owns a `ReplicaSet`, 
+For example, if you have a `Deployment` named `client`, which then creates and owns a `ReplicaSet`,
 which then creates and owns a `Pod`, then the service name for that pod is `client` - same as the name of the `Deployment`.
 The goal is to generate a mapping that speaks in the same language that dev teams use.
 
 ## Exporting a network map
+
 The network mapper continuously builds a map of pod to pod communication in the cluster. The map can be exported at any time in either JSON or YAML formats with the Otterize CLI.
 
 The YAML export is formatted as `ClientIntents` Kubernetes resource files. Client intents files can be consumed by the [Otterize intents operator](https://github.com/otterize/intents-operator) to configure pod-to-pod access with network policies, or Kafka client access with Kafka ACLs and mTLS.
 
 ## Learn more
+
 Explore our [documentation](https://docs.otterize.com/) site to learn how to:
-- [Map pod-to-pod communication](https://docs.otterize.com/quick-tutorials/k8s-network-mapper).
-- [Automate network policies](https://docs.otterize.com/quick-tutorials/k8s-network-policies).
-- And more...
+
+* [Map pod-to-pod communication](https://docs.otterize.com/quick-tutorials/k8s-network-mapper).
+* [Automate network policies](https://docs.otterize.com/quick-tutorials/k8s-network-policies).
+* And more...
 
 ## Contributing
+
 1. Feel free to fork and open a pull request! Include tests and document your code in [Godoc style](https://go.dev/blog/godoc)
 2. In your pull request, please refer to an existing issue or open a new one.
 3. See our [Contributor License Agreement](https://github.com/otterize/cla/).
 
 ## Slack
+
 To join the conversation, ask questions, and engage with other users, join the Otterize Slack!
- 
+
 [![button](https://i.ibb.co/vwRP6xK/Group-3090-2.png)](https://joinslack.otterize.com)
 
 ## Usage telemetry
+
 The mapper reports anonymous usage information back to the Otterize team, to help the team understand how the software is used in the community and what aspects users find useful. No personal or organizational identifying information is transmitted in these metrics: they only reflect patterns of usage. You may opt out at any time through a single configuration flag.
 
 To **disable** sending usage information:
-- Via the Otterize OSS Helm chart: `--set global.telemetry.enabled=false`.
-- Via an environment variable: `OTTERIZE_TELEMETRY_ENABLED=false`.
-- If running a mapper directly: `--telemetry-enabled=false`.
+
+* Via the Otterize OSS Helm chart: `--set global.telemetry.enabled=false`.
+* Via an environment variable: `OTTERIZE_TELEMETRY_ENABLED=false`.
+* If running a mapper directly: `--telemetry-enabled=false`.
 
 If the `telemetry` flag is omitted or set to `true`, telemetry will be enabled: usage information will be reported.
 

src/shared/testbase/README.md

@@ -1,7 +1,10 @@
+# Testing instructions
+
 In order to run the tests locally, “envtest” requires some k8s binaries. To install them, run once:
-```
+
+```shell
 go install sigs.k8s.io/controller-runtime/tools/setup-envtest@latest
 source <(setup-envtest use -p env)
 sudo mkdir -p /usr/local/kubebuilder
 sudo ln -s "$KUBEBUILDER_ASSETS" /usr/local/kubebuilder/bin
-```
+```