Open HGCH81 opened 2 months ago
Hello,
You can review/change your token, it's better :) It's a important change since Kubernetes v1.28.
Better patch is (for me):
data=$(eval timeout "$TIMEOUT" kubectl get --raw "/$api_path" 2>&1 | grep -Eiv "(Warn|Deprecat)")
Thx
Hello,
with new kubernetes version v1.28.6 some cluster have problemes with secrets token like:
kubectl get node Warning: Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
this cause the exception: parse error: Invalid numeric literal at line 1, column 8
i have had "grep" condition in line 124:
I hope this can help other people, and if possible add this to the main script.
In some cases you need to add Decrecated either
| grep -i -v "Warn" | grep -i -v "Deprecat"
Thx