From 16c8cc0702d986d4316dab4dcdaa91f2a18574cd Mon Sep 17 00:00:00 2001 From: Sascha Grunert Date: Wed, 8 Dec 2021 09:25:44 +0100 Subject: [PATCH] Update content/en/blog/_posts/2021-12-13-security-profiles-operator-v0.4.0/index.md Co-authored-by: Tim Bannister --- .../2021-12-13-security-profiles-operator-v0.4.0/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2021-12-13-security-profiles-operator-v0.4.0/index.md b/content/en/blog/_posts/2021-12-13-security-profiles-operator-v0.4.0/index.md index 8d70283e00..c3992eb02b 100644 --- a/content/en/blog/_posts/2021-12-13-security-profiles-operator-v0.4.0/index.md +++ b/content/en/blog/_posts/2021-12-13-security-profiles-operator-v0.4.0/index.md @@ -86,7 +86,7 @@ which has changed is that the seccomp profile type `Architectures` now points to ### Metrics The operator now exposes metrics, which are described in detail in -[our new metrics documentation](https://github.com/kubernetes-sigs/security-profiles-operator/blob/71b3915/installation-usage.md#using-metrics). +our new [metrics documentation](https://github.com/kubernetes-sigs/security-profiles-operator/blob/71b3915/installation-usage.md#using-metrics). We decided to secure the metrics retrieval process by using [kube-rbac-proxy](https://github.com/brancz/kube-rbac-proxy), while we ship an additional `spo-metrics-client` cluster role (and binding) to retrieve the