chore: fix e2e testing on lower resources env

Author: devthejo

pkg/config/config.go

@@ -27,9 +27,9 @@ type Config struct {
 	LogFormat string `envconfig:"LOG_FORMAT" default:"auto" description:"Log format (auto, text, json)"`
 
 	// Node.js server configuration
-	HealthCheckWait     time.Duration `envconfig:"HEALTH_CHECK_WAIT" default:"30s" description:"Timeout for health check"`
-	HealthCheckInterval time.Duration `envconfig:"HEALTH_CHECK_INTERVAL" default:"500ms" description:"Interval for health check polling"`
-	NodeRequestTimeout  time.Duration `envconfig:"NODE_REQUEST_TIMEOUT" default:"30s" description:"Timeout for Node.js requests"`
+	HealthCheckWait     time.Duration `envconfig:"HEALTH_CHECK_WAIT" default:"900s" description:"Timeout for health check"`
+	HealthCheckInterval time.Duration `envconfig:"HEALTH_CHECK_INTERVAL" default:"1s" description:"Interval for health check polling"`
+	NodeRequestTimeout  time.Duration `envconfig:"NODE_REQUEST_TIMEOUT" default:"5s" description:"Timeout for Node.js requests"`
 
 	// Yarn configuration
 	MaxConcurrentYarnInstalls int `envconfig:"MAX_CONCURRENT_YARN_INSTALLS" default:"3" description:"Maximum concurrent yarn install operations"`

pkg/node/process.go

@@ -43,9 +43,9 @@ func NewProcessManager(gcInterval, idleTimeout time.Duration, tempDir string, lo
 		idleTimeout:         idleTimeout,
 		tempDir:             tempDir,
 		logger:              logger,
-		healthCheckWait:     90 * time.Second,     // Default timeout for health check
-		healthCheckInterval: 1 * time.Millisecond, // Default interval for health check polling
-		requestTimeout:      30 * time.Second,     // Default timeout for requests
+		healthCheckWait:     60 * time.Second, // Default timeout for health check
+		healthCheckInterval: 1 * time.Second,  // Default interval for health check polling
+		requestTimeout:      5 * time.Second,  // Default timeout for requests
 	}
 
 	// Apply options

tests/test-xfuncjs.sh

@@ -72,13 +72,13 @@ kubectl apply -f tests/fixtures/domain-sdk/sample.yaml
 # Wait for the ConfigMap to be created
 echo "Waiting for ConfigMap to be created..."
 configmap_created=false
-for i in {1..60}; do
+for i in {1..180}; do
   if kubectl get configmap generated-configmap -n test-xfuncjs &> /dev/null; then
     echo "ConfigMap created successfully!"
     configmap_created=true
     break
   fi
-  echo "Waiting for ConfigMap to be created... ($i/60)"
+  echo "Waiting for ConfigMap to be created... ($i/180)"
 
   # Check the status of the SimpleConfigMap
   if [ $((i % 5)) -eq 0 ]; then