Skip to content

Commit

Permalink
docs: Fix links to policy YAML files
Browse files Browse the repository at this point in the history
Signed-off-by: Michi Mutsuzaki <[email protected]>
  • Loading branch information
michi-covalent committed Oct 18, 2023
1 parent b987fe7 commit bdba0e6
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 10 deletions.
10 changes: 5 additions & 5 deletions docs/content/en/docs/getting-started/enforcement.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ export SERVICECIDR=$(kubectl describe pod -n kube-system kube-apiserver-kind-con
Then we can apply the egress cluster enforcement policy

```shell-session
wget http://github.com/cilium/tetragon/examples/quickstart/network_egress_cluster_enforce.yaml
wget https://raw.githubusercontent.com/cilium/tetragon/main/examples/quickstart/network_egress_cluster_enforce.yaml
envsubst < network_egress_cluster_enforce.yaml | kubectl apply -n default -f -
```

Expand Down Expand Up @@ -107,7 +107,7 @@ devices and raw sockets application may attempt.

The following extends the example from [File Access Monitoring]({{< ref "docs/getting-started/file-events" >}})
with enforcement to ensure sensitive files are not read. The policy used is the
[`file-monitoring-enforce.yaml`](https://github.com/cilium/tetragon/blob/main/examples/quickstart/file-monitoring-enforce.yaml)
[`file_monitoring_enforce.yaml`](https://github.com/cilium/tetragon/blob/main/examples/quickstart/file_monitoring_enforce.yaml)
it can be reviewed and extended as needed. The only difference between the
observation policy and the enforce policy is the addition of an action block
to sigkill the application and return an error on the op.
Expand All @@ -117,11 +117,11 @@ To apply the policy:
{{< tabpane lang=shell-session >}}

{{< tab Kubernetes >}}
kubectl delete -f http://github.com/cilium/tetragon/examples/quickstart/file_monitoring.yaml
kubectl apply -f http://github.com/cilium/tetragon/examples/quickstart/file_monitoring_enforce.yaml
kubectl delete -f https://raw.githubusercontent.com/cilium/tetragon/main/examples/quickstart/file_monitoring.yaml
kubectl apply -f https://raw.githubusercontent.com/cilium/tetragon/main/examples/quickstart/file_monitoring_enforce.yaml
{{< /tab >}}
{{< tab Docker >}}
wget http://github.com/cilium/tetragon/examples/quickstart/file-monitoring.yaml
wget https://raw.githubusercontent.com/cilium/tetragon/main/examples/quickstart/file_monitoring.yaml
docker stop tetragon-container
docker run --name tetragon-container --rm --pull always \
--pid=host --cgroupns=host --privileged \
Expand Down
6 changes: 3 additions & 3 deletions docs/content/en/docs/getting-started/file-events.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ remains low even on busy systems.

The following extends the example from Execution Tracing with a policy to
monitor sensitive files in Linux. The policy used is the
[`file-monitoring.yaml`](https://github.com/cilium/tetragon/blob/main/examples/quickstart/file-monitoring.yaml)
[`file_monitoring.yaml`](https://github.com/cilium/tetragon/blob/main/examples/quickstart/file_monitoring.yaml)
it can be reviewed and extended as needed. Files monitored here serve as a good
base set of files.

Expand All @@ -23,10 +23,10 @@ on disk.
{{< tabpane lang=shell-session >}}

{{< tab Kubernetes >}}
kubectl apply -f http://github.com/cilium/tetragon/examples/quickstart/file-monitoring.yaml
kubectl apply -f https://raw.githubusercontent.com/cilium/tetragon/main/examples/quickstart/file_monitoring.yaml
{{< /tab >}}
{{< tab Docker >}}
wget http://github.com/cilium/tetragon/examples/quickstart/file-monitoring.yaml
wget https://raw.githubusercontent.com/cilium/tetragon/main/examples/quickstart/file_monitoring.yaml
docker stop tetragon-container
docker run --name tetragon-container --rm --pull always \
--pid=host --cgroupns=host --privileged \
Expand Down
4 changes: 2 additions & 2 deletions docs/content/en/docs/getting-started/network.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ First we apply a policy that includes the `podCIDR` and `serviceIP` list as
filters to avoid filter out cluster local traffic. To apply the policy:

```shell-session
wget http://github.com/cilium/tetragon/examples/quickstart/network_egress_cluster.yaml
wget https://raw.githubusercontent.com/cilium/tetragon/main/examples/quickstart/network_egress_cluster.yaml
envsubst < network_egress_cluster.yaml | kubectl apply -f -
```

Expand Down Expand Up @@ -98,7 +98,7 @@ export SERVICECIDR="127.0.0.1/32"

To create the policy,
```shell-session
wget http://github.com/cilium/tetragon/examples/quickstart/network_egress_cluster.yaml
wget https://raw.githubusercontent.com/cilium/tetragon/main/examples/quickstart/network_egress_cluster.yaml
envsubst < network_egress_cluster.yaml > network_egress_cluster_subst.yaml
```

Expand Down

0 comments on commit bdba0e6

Please sign in to comment.