Скачать или смотреть Mastering Grep in Linux: Extracting NodePort and IP Addresses from Kubernetes Outputs

Discover effective `grep`, `awk`, and `sed` commands for extracting NodePort and IP addresses from Kubernetes command outputs in Linux.
---
This video is based on the question https://stackoverflow.com/q/64684523/ asked by the user 'niqo' ( https://stackoverflow.com/u/7589423/ ) and on the answer https://stackoverflow.com/a/64685037/ provided by the user 'Raman Sailopal' ( https://stackoverflow.com/u/7840440/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to grep following words from string

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Mastering Grep in Linux: Extracting NodePort and IP Addresses from Kubernetes Outputs

In the vast world of Linux, extracting specific data from command outputs is a common task that can save a considerable amount of time and improve efficiency. If you're working with Kubernetes and need to retrieve the NodePort from command outputs, or extract IP addresses without unnecessary clutter, this guide is just for you.

In the examples we'll cover, you'll learn how to use powerful tools like awk and sed to achieve your goals with precision. Let's dive into it!

Problem Overview

When you execute certain Kubernetes commands, the output can be quite verbose and contain multiple elements that may not always be relevant to what you are trying to accomplish. For instance, you may want to extract:

The NodePort (like 31000) from the line displaying the service details.

The IP address (like 192.168.99.213) from output information about the Kubernetes master, but you aim to exclude extra details like 8443 or https://.

Here’s a closer look at the command outputs we’re working with:

Example Command Outputs

The output for the NodePort includes lines like this:

[[See Video to Reveal this Text or Code Snippet]]

The output for the Kubernetes master might look like this:

[[See Video to Reveal this Text or Code Snippet]]

Solution Breakdown

Let’s explore how to extract the desired information from these outputs using awk and sed.

Extracting the NodePort with awk

To get the NodePort ('$31000$') for a specific Kubernetes service, you can use the following command:

[[See Video to Reveal this Text or Code Snippet]]

Explanation:

kubecmd is the command you run to retrieve the service details.

-F[:] sets the delimiter to :, which helps in parsing sections of the output.

NR>1 ensures we skip the header line of the output.

split($2, arr, "/") splits the second field (which contains both the port and NodePort) by / into an array called arr.

print arr[1] outputs the first element of the array, which corresponds to the NodePort you wish to extract.

Extracting IP Address with sed

To capture the IP address from the Kubernetes master message, you can use this command:

[[See Video to Reveal this Text or Code Snippet]]

Explanation:

This command utilizes sed for textual pattern substitution.

The -E flag allows for extended regular expressions.

The command s/(^.*Kubernetes master.*https://)(.*)(:.*$)/\2/p matches the entire output, breaking it down into three parts:

(^.*Kubernetes master.*https://): The first section that identifies the base string.

(.*): The second section matches the IP address, which you want.

(:.*$): The last section captures the remaining details (the port), which we don't need.

The \2 denotes that only the second section (the IP address) is printed, thanks to the p flag that specifies to print the substitution results.

Conclusion

This guide provides a robust method to utilize awk and sed for extracting relevant data from Kubernetes output formats in Linux. By mastering these commands, you can significantly streamline your workflow and ensure you are focusing on the most important elements of your output data.

So next time you process Kubernetes command outputs, try implementing these techniques and see how they can enhance your productivity! If you have any questions or need further assistance, feel free to reach out in the comments below.