Skip to content

Commit e4c0f32

Browse files
authored
Merge pull request #39206 from sftim/20230201_sig_instrumentation_spotlight_fixup
Fix up 2023 SIG Instrumentation spotlight article
2 parents d7e7824 + 660d5e1 commit e4c0f32

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/blog/_posts/2023-02-03-sig-instrumentation-spotlight.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ canonicalUrl: https://www.kubernetes.dev/blog/2023/02/03/sig-instrumentation-spo
1010

1111
Observability requires the right data at the right time for the right consumer (human or piece of software) to make the right decision. In the context of Kubernetes, having best practices for cluster observability across all Kubernetes components is crucial.
1212

13-
SIG Instrumentation helps to address this issue by providing best practices and tools that all other SIGs use to instrument Kubernetes components-like the *Api server*, *scheduler*, *kubelet* and *kube-controller-manager*.
13+
SIG Instrumentation helps to address this issue by providing best practices and tools that all other SIGs use to instrument Kubernetes components-like the *API server*, *scheduler*, *kubelet* and *kube-controller-manager*.
1414

1515
In this SIG Instrumentation spotlight, [Imran Noor Mohamed](https://www.linkedin.com/in/imrannoormohamed/), SIG ContribEx-Comms tech lead talked with [Elana Hashman](https://twitter.com/ehashdn), and [Han Kang](https://www.linkedin.com/in/hankang), chairs of SIG Instrumentation, on how the SIG is organized, what are the current challenges and how anyone can get involved and contribute.
1616

0 commit comments

Comments
 (0)