feedcode

第二个是将来时态，还没有行政令。
Trump Says the U.S. Will Institute $100,000 Fee for Skilled Worker Visas

这个差别可大了，Trump Always Chickens Out (TACO)

不要 rewrite query parameter

nginx.ingress.kubernetes.io/configuration-snippet: |
if ($request_uri ~ "/dhq/([^\?]*)") {
set $path1 $1;
rewrite ^/dhq/ /$path1 break;
}

这个不是 ingress 的问题！
你只是恰巧用了 nginx ，解决方法
https://my.f5.com/manage/s/article/K000148648
试试在 configuration-snippet 再加一个
rewrite ^ $request_uri;

删掉 PV 后重建，记得 spec.claimRef 保持和之前的一样，PVC 会重新 Bound

while read share;do
echo "check $share"
kubectl get pv $share -o yaml > "$share-origin.yaml"
ns=$(yq '.spec.claimRef.namespace' "$share-origin.yaml")
pvc=$(yq '.spec.claimRef.name' "$share-origin.yaml")
echo "$ns $pvc"
if [ ! -f "all-pods-$ns.yaml" ] ;then
kubectl get pods -n $ns -o yaml > "all-pods-$ns.yaml"
fi
podname=$(yq ".items[]|select(.spec.volumes[].persistentVolumeClaim.claimName==\"$pvc\")|.metadata.name" "all-pods-$ns.yaml")
echo "pods $podname will be deleted"
# patch pv
kubectl patch pv $share -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}, "metadata":{"finalizers":null }}' --type=merge
kubectl delete pv $share --wait=false
sleep 5
kubectl delete pod -n $ns $podname
sleep 10
kubectl get pv $share || echo deleted
# recreate PV here
sed -e "REPLACE-HERE" "$share-origin.yaml" >"$share-new.yaml"
kubectl create -f "$share-new.yaml"
done<pv-shares.txt

ctr 不走 containerd 的 plugin 配置，plugins."io.containerd.grpc.v1.cri".registry 对 ctr 无用

The ctr utility is a command-line interface for directly interacting with the containerd daemon. It uses containerd's native API, not the CRI plugin's API. Therefore, when you use ctr image pull, it does not consult the registry mirror configurations set up for the CRI plugin.

你如果认为这里应该是或的关系，那改成|就行了

(?x) 这个表示 Free-Spacing ， 后面的空格和换行会 ignore
https://www.regular-expressions.info/freespacing.html

胃痉挛疼的厉害的时候一滴水都喝不下，只能打阿托品舒缓平滑肌