Open cdenneen opened 4 years ago
Hello!
Thank you for reaching out. The existing cluster with eksctl does not handle(From what I can see) the kubectl and helm lambda's that the core-workload utilizes to build it.
If you wanted to consume your eksctl
created cluster, I would recommend running the jfrog-artifactory-core-infrastructure.template.yaml
which will build the RDS and S3 with the output of access details. I would then follow the JFrog Artifactory HA ChartsWhich we are using in behind the scenes.
If you created an EKS cluster utilizing the EKS Quickstart The lambda's would be created and you could separately create the core-core-infrastucture and core-workload.
Hope that helps!
Would be useful to use this QS guide with existing EKS cluster provisioned using
eksctl
. Options would have to allow for:artifactory-primary
andartifactory-secondary
) - (helm install/upgrade instructions + CloudFormation) Either case would still require CF to stand up additional resources (S3, RDS, SecretsManager, etc)