Differences

This shows you the differences between two versions of the page.

--- findstr_a_grep_alternative_for_windows [2025/03/24 10:51] – walkeradmin
+++ findstr_a_grep_alternative_for_windows [2025/03/24 10:58] (current) – walkeradmin
@@ Line 14: / Line 14: @@
 The response will be:
-\\
 \\
 <code>
@@ Line 81: / Line 80: @@
 packaging-origin-server-64b75c54ff-pd4wh               7/7     Running   7 (76d ago)   76d
 license-manager-0                                      2/2     Running   5 (76d ago)   76d
+</code>
+However, If I was only interested in say 'srt' I could use grep to filter the response.
+\\
+    kubectl -n mediakind get pods |grep srt
+This would return just any lines that contain 'srt'
+\\
+<code>
+srt-worker-launcher-dcf66587-vg288                     1/1     Running   1 (76d ago)   76d
+srt-config-5784dd8f46-2twbd                            1/1     Running   1 (76d ago)   76d
+srt-ui-connector-6f6bdbd4c9-f2qtd                      1/1     Running   1 (76d ago)   76d
 </code>
+So grep is a fantastic tool for this, however, grep is not in Windows.
+\\
+\\
+----
+==== findstr ====
+What is in Windows (and I am using Windows 11-21H2, which is quite old) is something called 'findstr'. The syntax for findstr is very similar. Please bear in mind that grep may do more things that findstr, I am just using this one use case of filtering results from issued commands.
+\\
+    kubectl -n medikind get pods | findstr srt
+<code>
+srt-fe7a53f67-srt-worker-launcher-54796fb846-r8mpz                2/2     Running   0             58m
+srt-mux-vvltle-main-egress-srt-mux-vvltle-main-6756b5b7d-z52ng    2/2     Running   0             22m
+srt-mux-vvltle-main-srt-worker-launcher-68bfccb69c-94vsq          2/2     Running   0             23m
+</code>
+So findstr works very well in this use case.
+\\
+\\
+----