Closed ironmike-au closed 2 years ago
This bug is filed against an unsupported kOps version. At minimum upgrade to 1.20 and see if the behavior persists.
Is it safe to upgrade to kops 1.20 without completing the upgrade instructions for 1.18?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
/kind bug
1. What
kops
version are you running? The commandkops version
, will display this information. Version 1.18.3 (git-11ec695516)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 akops
flag.3. What cloud provider are you using? AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
5. What happened after the commands executed? We receive an error:
6. What did you expect to happen? To be able to complete the required actions
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? Initially this command was run through an SSO login and I though that might be a problem, so I started fresh with a direct IAM account configured simply using
aws configure
, but this didn't make any difference.I've confirmed that the cluster is healthy and normal kops commands run fine (such as
kops-1.18.3 validate cluster
)I've also confirmed that my account can pull perform the get-bucket-location command, though I'm not sure how relevant that is.
The bucket is in the same region as and AWS account as everything else, so there should be no cross-account permissions issues.
Thanks in advance for any help you can offer!