Open akashsuresh opened 3 years ago
Hello - I have the same issue following the steps in the readme.
From the jx admin log
it seems this may be the culprit:
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
Any ideas how to resolve the issue?
Please update to the latest version of the eks-jx module, it's fixed there: https://github.com/jenkins-x/terraform-aws-eks-jx/releases
I think this may be related to issue #20 , I'll repost my setup here incase it helps. I just experienced the same issue on EKS 1.15.46. here is my setup main.tf
module "eks-jx" {
source = "jenkins-x/eks-jx/aws"
version = "1.15.46"
...
}
variables.tf
variable "cluster_version" {
description = "Kubernetes version to use for the EKS cluster."
type = string
default = "1.21"
}
variable "nginx_chart_version" {
type = string
description = "nginx chart version"
default = "3.12.0"
}
I just retried with cluster_version 1.20 instead of 1.21 and I'm still running into this issue. @ankitm123 what information do you need from me to be able to debug this?
Still the same issue . Also GKE version faces the same problem . Is this a terraform bug by any chance ?
I do see the same problem. Downgrading versions is not helping
What is the output of the external-secrets pod in the secret-infra
namespace and vault pod in the jx-vault
namespace?
I appear to be having the same issue, and I'm seeing the following on the external-secrets
pod in the secret-infra
namespace;
I got the same issue. EKS: 1.20 and 1.21
I have three private subnets in advance.
And I use the latest version of eks-jx
.
Then, jx admin log
output is:
The below are suspicious errors in pods.
I installed JX on EKS but secrets don't seem to have auto populated. Any reason why this would have happened?