Disable logger development mode to avoid panicking

giantswarm · Aug 14, 2024 · f956128 · f956128
1 parent 5aaa07f
commit f956128
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -7,9 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed
+
+- Disable logger development mode to avoid panicking
+
 ## [0.15.0] - 2024-04-17
 
 ### Changed
+
 - Update capa to v2.3.0.
 - Use ResourceID instead of ID for CAPA Subnets.
 

diff --git a/controllers/controllers_suite_test.go b/controllers/controllers_suite_test.go
@@ -69,7 +69,6 @@ var _ = BeforeSuite(func() {
 	}
 	logger = zap.New(zap.UseFlagOptions(&opts))
 	logf.SetLogger(logger)
-	logf.SetLogger(zap.New(zap.WriteTo(GinkgoWriter), zap.UseDevMode(true)))
 
 	tests.GetEnvOrSkip("KUBEBUILDER_ASSETS")
 

diff --git a/main.go b/main.go
@@ -105,7 +105,7 @@ func main() {
 	flag.StringVar(&workloadClusterBaseDomain, "basedomain", "", "Domain for workload cluster, e.g. installation.eu-west-1.aws.domain.tld")
 
 	opts := zap.Options{
-		Development: true,
+		Development: false,
 		TimeEncoder: zapcore.RFC3339TimeEncoder,
 	}
 	opts.BindFlags(flag.CommandLine)