Followed these instructions: https://s3.amazonaws.com/core-aws-launcher/README.html
deploying to eu-west-1
Cloudformation shows success for core, vpc-stack and eks-workers.
In the setup guide I can ssh to the controller node but only namespaces are:
[ec2-user@ip-XX-XX-XX-XX ~]$ kubectl get namespaces
NAME STATUS AGE
default Active 3h
kube-public Active 3h
kube-system Active 3h
[
docker images shows no images.
Any help greatly appreciated.
Hi Nigel,
Thank you for bringing this to our attention. We are aware of the deployment issues with the CloudBees Core on AWS Marketplace solution:
(1) https://aws.amazon.com/marketplace/pp/B07JQ19L5T
(2) https://github.com/cloudbees/core-aws-launcher
The AWS Marketplace solution was created before the launch of a new EKS Quick Start framework:
(1) https://aws.amazon.com/quickstart/architecture/amazon-eks/
(2) https://github.com/aws-quickstart/quickstart-amazon-eks
We have recently built a CloudBees Core AWS Quick Start on top of the new framework:
(1) https://aws.amazon.com/quickstart/architecture/cloudbees-core/
(2) https://github.com/aws-quickstart/quickstart-cloudbees-core
We intend to update the AWS Marketplace CloudFormation templates with the newer Quick Start templates. Both solutions currently use a “bring your own license” (BYOL) model. For these reasons, we recommend using the Quick Start to deploy CloudBees Core on AWS.
Thanks,
David
