Merge pull request #43299 from steve-hardman/fix-jq-link

Update outdated jq link

Author: k8s-ci-robot

content/en/blog/_posts/2020-09-03-warnings/index.md

@@ -63,7 +63,7 @@ This metric has labels for the API `group`, `version`, `resource`, and `subresou
 and a `removed_release` label that indicates the Kubernetes release in which the API will no longer be served.
 
 This is an example query using `kubectl`, [prom2json](https://github.com/prometheus/prom2json),
-and [jq](https://stedolan.github.io/jq/) to determine which deprecated APIs have been requested
+and [jq](https://jqlang.github.io/jq/) to determine which deprecated APIs have been requested
 from the current instance of the API server:
 
 ```sh

content/en/blog/_posts/2021-10-18-kpng-specialized-proxiers.md

@@ -210,7 +210,7 @@ podip=$(cat /tmp/out | jq -r '.Endpoints[]|select(.Local == true)|select(.IPs.V6
 ip6tables -t nat -A PREROUTING -d $xip/128 -j DNAT --to-destination $podip
 ```
 
-Assuming the JSON output above is stored in `/tmp/out` ([jq](https://stedolan.github.io/jq/) is an *awesome* program!).
+Assuming the JSON output above is stored in `/tmp/out` ([jq](https://jqlang.github.io/jq/) is an *awesome* program!).
 
 
 As this is an example we make it really simple for ourselves by using

content/en/docs/reference/kubectl/cheatsheet.md

@@ -213,7 +213,7 @@ kubectl get pods --field-selector=status.phase=Running
 kubectl get nodes -o jsonpath='{.items[*].status.addresses[?(@.type=="ExternalIP")].address}'
 
 # List Names of Pods that belong to Particular RC
-# "jq" command useful for transformations that are too complex for jsonpath, it can be found at https://stedolan.github.io/jq/
+# "jq" command useful for transformations that are too complex for jsonpath, it can be found at https://jqlang.github.io/jq/
 sel=${$(kubectl get rc my-rc --output=json | jq -j '.spec.selector | to_entries | .[] | "\(.key)=\(.value),"')%?}
 echo $(kubectl get pods --selector=$sel --output=jsonpath={.items..metadata.name})
 

content/en/docs/tasks/administer-cluster/verify-signed-artifacts.md

@@ -15,7 +15,7 @@ You will need to have the following tools installed:
 
 - `cosign` ([install guide](https://docs.sigstore.dev/cosign/installation/))
 - `curl` (often provided by your operating system)
-- `jq` ([download jq](https://stedolan.github.io/jq/download/))
+- `jq` ([download jq](https://jqlang.github.io/jq/download/))
 
 ## Verifying binary signatures
 

content/en/docs/tasks/tls/managing-tls-in-a-cluster.md

@@ -36,7 +36,7 @@ You need the `cfssl` tool. You can download `cfssl` from
 
 Some steps in this page use the `jq` tool. If you don't have `jq`, you can
 install it via your operating system's software sources, or fetch it from
-[https://stedolan.github.io/jq/](https://stedolan.github.io/jq/).
+[https://jqlang.github.io/jq/](https://jqlang.github.io/jq/).
 
 <!-- steps -->
 
@@ -267,7 +267,7 @@ kubectl get csr my-svc.my-namespace -o json | \
 ```
 
 {{< note >}}
-This uses the command line tool [`jq`](https://stedolan.github.io/jq/) to populate the base64-encoded
+This uses the command line tool [`jq`](https://jqlang.github.io/jq/) to populate the base64-encoded
 content in the `.status.certificate` field.
 If you do not have `jq`, you can also save the JSON output to a file, populate this field manually, and
 upload the resulting file.