Closed nishantn3 closed 2 years ago
Disable kuberhealthy, and it will work. https://github.com/jenkins-x/terraform-aws-eks-jx/blob/4240b95efe7558de35eb195d4b3ad76fbe9d0f20/variables.tf#L475 (in tf file, set this to false). it's an upstream issue with kuberhealthy, and not jx.
@ankitm123
I have not installed kuberhealthy anyway. Since it required a remote install from terraform I disabled it.
Note: I have customized the EKS terraform code to use my custom EKS module to deploy private EKS(control plane private)
@ankitm123
Hi,
I was able to make some progress. Now stuck at this
error: failed to find hmac token from secret: could not find lighthouse hmac token lighthouse-hmac-token in namespace jx: secrets "lighthouse-hmac-token" not found
make: *** [versionStream/src/Makefile.mk:216: gitops-webhook-update] Error 1
Can you help?
Closing, I could fix and deploy Jenkins-X. As I was not using the terraform repo for eks by jenkins-x I was facing some issues that I have figured out
I have deployed using a separate method. Though I have deployed eks, roles and other resources using terraform template but I am deploying the
jx/jx-git-operator
manually using helm since our cluster is completely private and terraform cloud is not able to communicate with it.I have applied the
terraform-jx-requirements
configmap andjx/jx-git-operator
helm chart manually. I have also the the variables required to run this chart.The jx-git-operator pod is up and running but the jx-boot job is failing. At the end I see that kubectl apply is failing at line 291. Where the customresourcedefinitions are getting applied from
config-root
folder. So I copied theconfig-root
folder from pod and tried running it from the host and it is failing witherror: no objects passed to apply
.I am adding the logs below from the jx-boot pod.
Please let me know if you need any other logs.
Thanks.