-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This blueprint does not spin up any pods/nodes #175
Comments
@freschri ^^ The pattern is expected to provision the backstage addon and default settings for nodegroup. I see it is declared here: https://github.com/aws-samples/cdk-eks-blueprints-patterns/blob/main/lib/backstage-construct/index.ts#L71 You should see the nodes and pods of the addons that are provisioned. |
thanks @omi-jbrivero could you please expand on the problem description? e.g. what's the output log? thanks |
I am getting a 503 error, upon checking EKS cluster, there is no running nodes/pods. |
This issue has been automatically marked as stale because it has been open 60 days |
Issue closed due to inactivity. |
Hello,
I was trying to setup for the first time: https://aws.amazon.com/blogs/opensource/building-developer-portals-with-backstage-and-amazon-eks-blueprints/
This blueprint does not spin up any pods/nodes but turns out it does not spin up any nodes.
Are anyone also experiencing same issue?
Thanks!
The text was updated successfully, but these errors were encountered: