Could not read kubernetes Secrets using cluster client

[romaine-murray]

Hi I am encountering this issue when trying to port a GKE cluster to EKC.

Here are the version info of the applications in use. Kubectl: Client Version: v1.27.2 Kustomize Version: v5.0.1 Server Version: v1.27.3-gke.100

Helm: v3.10.1+g9f88ccb

Docker: Docker version 24.0.5, build ced0996

KMF v1.1.0 NB: I am using WSL2 with the ubuntu distro version 22.04

Here is a screenshot of the error I'm receiving as well.

[vasarobi]

@romaine-murray - We will look at this issue and it could be because new helm manages some secret differently. Meanwhile you can pick the package in release section to test.

[khanhnd0408]

@romaine-murray - Have you found a solution for it? I'm facing the same issue; this error was raised from the Generate_cronjob_config function. I'm using Kubectl 1.26, Helm 3.8, and KMF 1.1.0.

logs:

Please pass the location of source kubernetes cluster kubeconfig file: ********
Please pass the source context (default: **********): 
Please pass source type  (supported source types GKE,AKS,KOPS): GKE
Deploy
GKE Resources
GKE GetSourceDetails....
Namespace list entered by user
cronjob: default
Could not read kubernetes Secrets using cluster client: the server could not find the requested resource

[romaine-murray]

Hi @khanhnd0408, our team have since abandoned this workflow and opted to deploy into AWS EKS manually, as we were strapped for time, maybe another time we'll be able to investigate this issue further.

[victor-fonne-neoxia]

Hi

is there a solution for that?

[kanapp]

@vasarobi we are having the below issue and additionally we've attempted with all tags (v1.1.2.0,v1.1.0,v1.0.0)

Error1: Used branch main

Deploy GKE Resources GKE GetSourceDetails.... Namespace list entered as 'all' by user, hence all namespaces will be considered Could not read kubernetes Secrets using cluster client: the server could not find the requested resource

Error 2: Used branch dependabot/go_modules/helm.sh/helm/v3-3.14.2

Deploy GKE Resources GKE GetSourceDetails.... Namespace list entered as 'all' by user, hence all namespaces will be considered 2024/03/06 07:55:40 exit status 1

[vasarobi]

@vasarobi we are having the below issue and additionally we've attempted with all tags (v1.1.2.0,v1.1.0,v1.0.0)

Error1: Used branch main

Deploy GKE Resources GKE GetSourceDetails.... Namespace list entered as 'all' by user, hence all namespaces will be considered Could not read kubernetes Secrets using cluster client: the server could not find the requested resource

Error 2: Used branch dependabot/go_modules/helm.sh/helm/v3-3.14.2

Deploy GKE Resources GKE GetSourceDetails.... Namespace list entered as 'all' by user, hence all namespaces will be considered 2024/03/06 07:55:40 exit status 1

@Mahendrasiddappa

Apologies for any inconvenience. We acknowledge the problem arising from Helm. At this time, we haven't established a plan to address this issue. If you are not planning on helm migration then pls disable the Helm section in the source code and attempt running the package.

[siddhantprateek]

@vasarobi can you give more context on disabling the Helm section in the source code. I tried removing all helm related methods, still encountering the same issue. Is there any forked repository having disabled Helm section?

[vasarobi]

@vasarobi can you give more context on disabling the Helm section in the source code. I tried removing all helm related methods, still encountering the same issue. Is there any forked repository having disabled Helm section?

@siddhantprateek - The libraries & packages have to be updated to use the latest ones. You can comment out helm in below section.

file: aws-kubernetes-migration-factory/app/source/gke/gke.go code: source_impl.Generate_helm_charts(sCluster, &resources)