You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. What kops version are you running? The command kops version, will display
this information.
Client version: 1.30.1 (git-v1.30.1)
2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.
Server Version: v1.29.7
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
When upgrading from kOps v1.29.2 -> v1.30.1 we are receiving some DEBUG messages from the aws-sdk when running command like kops update cluster from a laptop (outside of AWS).
6. What did you expect to happen?
No failed requests, however it does not seem to be causing an error or preventing us from upgrading.
7. Please provide your cluster manifest. Execute kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.
8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.
9. Anything else do we need to know?
This looks related to the aws-sdk-go-v2 migration in #16424, and it seems like the fallback in #16778 is working as expected but it would be nice to suppress these messages.
The text was updated successfully, but these errors were encountered:
/kind bug
1. What
kops
version are you running? The commandkops version
, will displaythis information.
Client version: 1.30.1 (git-v1.30.1)
2. What Kubernetes version are you running?
kubectl version
will print theversion if a cluster is running or provide the Kubernetes version specified as
a
kops
flag.Server Version: v1.29.7
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
When upgrading from kOps
v1.29.2
->v1.30.1
we are receiving some DEBUG messages from the aws-sdk when running command likekops update cluster
from a laptop (outside of AWS).5. What happened after the commands executed?
6. What did you expect to happen?
No failed requests, however it does not seem to be causing an error or preventing us from upgrading.
7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml
to display your cluster manifest.You may want to remove your cluster name and other sensitive information.
8. Please run the commands with most verbose logging by adding the
-v 10
flag.Paste the logs into this report, or in a gist and provide the gist link here.
9. Anything else do we need to know?
This looks related to the aws-sdk-go-v2 migration in #16424, and it seems like the fallback in #16778 is working as expected but it would be nice to suppress these messages.
The text was updated successfully, but these errors were encountered: