Experiencing Terraformer init while validating claudie Operator

[chaitu7989]

Current Behaviour when i am creating the on-prem/AWS cluster i am facing the issue with Terraformer, i have tried with v.0.8.1 as well as v.0.7.3, in both the versions i am getting the same Error.

Expected Behaviour It must give the build succesfully completed with the claudie operator img width="644" alt="Terra-3" src="https://github.com/berops/claudie/assets/152254254/eb1c1611-ee04-49a7-8614-fa7f17d4a5e7"> Steps To Reproduce

Example: steps to reproduce the behaviour:

1. In kubernetes cluster with version v1.30.1

2. Inputmanifest apiVersion: claudie.io/v1beta1 kind: InputManifest metadata: name: privateclusterexample labels: app.kubernetes.io/part-of: claudie spec: nodePools: static:

   • name: control nodes:
     • endpoint: "10.1.149.73" secretRef: name: static-node-key namespace: on-prem-test
   • name: compute nodes:
     • endpoint: "10.1.149.74" secretRef: name: static-node-key namespace: on-prem-test
     • endpoint: "10.1.149.75" secretRef: name: static-node-key namespace: on-prem-test kubernetes: clusters:
   • name: private-cluster version: v1.26.13 network: 192.168.2.0/24 pools: control: - control compute: - compute

3. Run kubectl apply -f <inputmanifest.yaml>

4. Error

Anything else to note

Please get back to us ASAP with the suitable solution.

[Despire]

Hi @chaitu7989, sorry for the delay.

From the provided logs we can't really figure out what did go wrong.

I would advice setting the log level to debug (there will be more detailed logs present)

If you already have claudie deployed you can simply edit the env config map that can be found in the claudie namespace.

 kubectl get cm -n claudie
NAME                            DATA   AGE
...
env-<some number>                  18     121d
...

kubectl edit cm env-<some number> -n claudie

You need to change the info log to debug

 ...
 
  GOLANG_LOG: info    ->    GOLANG_LOG: debug 
  
 ...

After editing the ConfigMap you need to restart the pods.