Open cnukwas opened 1 year ago
I see same error with the boot pod even with install_kuberhealthy = false
. I wonder how others are able to install this on any recent Kubernetes versions since this issue appears to be there in 2022.
error validating "config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-bot-token-kuberhealthycheck.yaml": error validating data: ValidationError(KuberhealthyCheck.spec.podSpec.containers[0]): unknown field "restartPolicy" in io.github.comcast.v1.KuberhealthyCheck.spec.podSpec.containers; if you choose to ignore these errors, turn validation off with --validate=false
error validating "config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-events-kuberhealthycheck.yaml": error validating data: ValidationError(KuberhealthyCheck.spec.podSpec.containers[0]): unknown field "restartPolicy" in io.github.comcast.v1.KuberhealthyCheck.spec.podSpec.containers; if you choose to ignore these errors, turn validation off with --validate=false
error validating "config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-kuberhealthycheck.yaml": error validating data: ValidationError(KuberhealthyCheck.spec.podSpec.containers[0]): unknown field "restartPolicy" in io.github.comcast.v1.KuberhealthyCheck.spec.podSpec.containers; if you choose to ignore these errors, turn validation off with --validate=false
secret/webhook-certs unchanged
make[1]: *** [versionStream/src/Makefile.mk:324: kubectl-apply] Error 1
make[1]: Leaving directory '/workspace/source'
error: failed to regenerate: failed to regenerate phase 1: failed to run 'make regen-phase-1 NEW_CLUSTER=false' command in directory '.', output: ''
I was able to resolve both errors related to kuberhealthy deployments by making below changes to the Terraform configuration and didn't have to disable kuberhealthy in the TF configuration. I will create a PR if time permits since many people have run into similar issues with kuberhealthy in 1.24 and later k8s versions.
.terraform/modules/eks-jx.health.jx-health/main.tf -- update kuberhealthy helm_release version from 64 to 92 and update jx_kh_check_version variable from 0.0.78 to 0.0.80 in .terraform/modules/eks-jx.health.jx-health/variables.tf
Summary
I am new to Jenkins-x and having trouble with the installation on EKS using Secrets Manager with Terraform installation approach. Seeing these errors. Any help is really appreciated. I did make a dummy commit to our internal bitbucket cluster repo(jx3-eks-asm) and still seeing same errors, I believe it's because the boot pods are failing as well. Here are the errors from health status command.
There were bunch of other issues too but was able to resolve by making local changes to kuberhealthy and other helm chart versions. I have verified that we have terraform, aws-cli, aws-iam-authenticator, and wget as mentioned in the prerequisites section. Noticed that none of the health commands work if kuberhealthy is disabled and it appears that there are bunch of issues with that Helm chart and CRDs installation. Its using an old version of the chart, so I updated to 0.0.90 or similar to fix another issue but now seeing this.
Error from one of boot pods in the jx-git-operator ns:
Steps to reproduce the behavior
Install Jenkins-x using latest Terraform module on EKS Configured Kubernetes cluster version to 1.24 Use AWS Secrets Manager Clone jx3-gitops-repositories/jx3-terraform-eks to a bitbucket local repo and push changes to internal remote bitbucket cloud repo Clone https://github.com/jx3-gitops-repositories/jx3-eks-asm repo to update jx-requirments.yaml to point to bitbucket cloud URL and other information as per https://jenkins-x.io/v3/admin/setup/config/git/#bitbucket-cloud
Expected behavior
jx boot pods and gitops operator pods start normal but seeing errors with healthcheck related pods.
Actual behavior
Terraform version
terraform version Terraform v1.4.5 on linux_amd64
main.tf content:
Module version
https://registry.terraform.io/modules/jenkins-x/eks-jx/aws/latest
Operating system
Linux