-
Notifications
You must be signed in to change notification settings - Fork 41
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
Install fails on eks 1.21 #27
Comments
You have to wait for 2 PRs to be merged before you can use jx with kubernetes 1.21 with vault: jenkins-x-charts/vault-instance#12 and jenkins-x/terraform-aws-eks-jx#320 You can check the logs of the external secrets in the secret-infra namespace and vault pods in the jx-vault namespace, and see that it has issues around iss. |
@mestuddtc Those PRs have been merged, can you update the version of the eks-jx module to the latest, and run an apply again? https://github.com/jenkins-x/terraform-aws-eks-jx/releases/tag/v1.17.3 |
terraform apply fails with the following error:
|
Looks like an update is needed in https://github.com/jenkins-x-charts/vault-instance/blob/master/charts/vault-instance/values.yaml I could open a PR for that, but I wouldn't know how to test it. |
@mestuddtc the latest version of the eks-jx module has ur changes, try it and let me know if it works! |
@ankitm123 it does successfully install - the boot job completed, and the secrets are populated with no secret errors from any pods. There are four things reported by
Occasionally those pods show up, but they're always deleted before I can view them. There are
And the
I haven't had time yet to investigate. I'm not sure if those should be a separate bug? |
I think that's a kuberhealthy issue, James is looking at it I believe, but it's just a monitoring tool, and not a blocker (and unrelated to eks), so it will get fixed soon. |
Ok, good to know. |
I tried creating jenkins x cluster by:
terraform apply
Secrets appear to never be created and various pods never start (similar to #16)
If I destroy the deployment, delete all state files, delete and re-template the cluster repo, change the cluster_version to 1.20, and run
terraform apply
again, jenkins x eventually comes up with everything running. (In contrast to report in #22. Deleting the cluster repo is required, as changes made by jx seem to prevent a new deploy from working.)jx admin log for 1.21:
The text was updated successfully, but these errors were encountered: