Feat/harness ccm autostopping/logging (#3)

* autostopping: add log levels for troubleshooting

* bump controller and chart version

.gitignore

@@ -0,0 +1 @@
+Makefile

charts/harness-ccm-autostopping/Chart.yaml

@@ -15,10 +15,10 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.2
+version: 0.1.3
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "1.1.9"
+appVersion: "1.2.1"

charts/harness-ccm-autostopping/README.md

@@ -28,6 +28,13 @@ helm upgrade -i harness-autostopping --namespace harness-autostopping --create-n
 - connectorId: the ID for the CCM K8s connector for this cluster
 - apiToken: a Harness API key with at least ccm:admin for all account level resources
 
+## troubleshooting
+
+to turn on debug logging, you can set the following values:
+```yaml
+router.logLevel: debug
+```
+
 ## development notes
 
 things that must be hard-coded:

charts/harness-ccm-autostopping/templates/router-deployment.yaml

@@ -36,6 +36,8 @@ spec:
           args:
           - -c
           - /etc/envoy.yaml
+          - --log-level
+          - {{ .Values.router.logLevel }}
           ports:
           - containerPort: 10000
             protocol: TCP

charts/harness-ccm-autostopping/values.yaml

@@ -64,6 +64,9 @@ router:
     pullPolicy: IfNotPresent
     tag: v1.18-latest
 
+  # set log via ENVOY_LOG_LEVEL: trace, debug, info, warning/warn, error, critical, off
+  logLevel: warning
+
   podAnnotations: {}
 
   podSecurityContext: {}