aws-ts-eks-distro error
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 894
- Avg merge
- 12h 19m
- Merged PRs (30d)
- 39
Description
running the aws-ts-eks-distro example without performing any changes to the code.
Expected behavior
stack should be created
Current behavior
getting the following error:
Diagnostics:
pulumi-nodejs:dynamic:Resource (cluster):
error: Command failed: kops create --name luke.cluster.pulumi-demos.net --state s3://kops-state-store-81a56ad -f -
error: error creating cluster: spec.metricsServer.insecure: Forbidden: Secure metrics server requires that cert manager is enabled
pulumi:pulumi:Stack (aws-ts-eks-distro-zigi):
error: error creating cluster: spec.metricsServer.insecure: Forbidden: Secure metrics server requires that cert manager is enabled
error: update failed
Steps to reproduce
pulumi up
Context (Environment)
➜ aws-ts-eks-distro git:(master) kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T21:15:16Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
➜ aws-ts-eks-distro git:(master) kops version
Version 1.20.0
Affected feature
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the aws-ts-eks-distro example and reproduce the failure with pulumi up, using the reported kops and kubectl versions as context. Trace the cluster configuration related to metrics server and cert manager, then verify that the stack can be created successfully without the reported kops diagnostic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, typescript
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100