http-add-on
http-add-on copied to clipboard
keda-add-ons-http-external-scaler pod won't work after installation
Report
I try to install http-add-on via helm, but keda-add-ons-http-external-scaler won't work after installation.
I use the following command to install latest version of http-add-on:
helm install http-add-on kedacore/keda-add-ons-http --create-namespace --namespace keda --set images.tag=canary
I copied the command from the install.md .
Expected Behavior
$ kubectl get deploy -n keda
NAME READY UP-TO-DATE AVAILABLE AGE
keda-add-ons-http-controller-manager 1/1 1 1 116s
keda-add-ons-http-external-scaler 1/1 1 1 116s
keda-add-ons-http-interceptor 1/1 1 1 116s
Actual Behavior
$ kubectl get deploy -n keda
NAME READY UP-TO-DATE AVAILABLE AGE
keda-add-ons-http-controller-manager 1/1 1 1 116s
keda-add-ons-http-external-scaler 0/1 1 0 116s
keda-add-ons-http-interceptor 1/1 1 1 116s
Steps to Reproduce the Problem
- helm install http-add-on kedacore/keda-add-ons-http --create-namespace --namespace keda --set images.tag=canary
- kubectl get po -n keda
- kubectl logs -f keda-add-ons-http-external-scaler-7f4746786c-cn2vc -n keda
Logs from KEDA HTTP operator
Here are logs from keda-add-ons-http-external-scaler pod:
$ kubectl logs -f keda-add-ons-http-external-scaler-7f4746786c-cn2vc -n keda
panic: required key KEDA_HTTP_SCALER_TARGET_ADMIN_DEPLOYMENT missing value
goroutine 1 [running]:
github.com/kelseyhightower/envconfig.MustProcess(...)
/go/pkg/mod/github.com/kelseyhightower/[email protected]/envconfig.go:233
main.mustParseConfig()
/go/src/github.com/kedacore/http-add-on/scaler/config.go:45 +0x5f
main.main()
/go/src/github.com/kedacore/http-add-on/scaler/main.go:37 +0x112
What version of the KEDA HTTP Add-on are you running?
0.3.0
Kubernetes Version
Other
Platform
Other
Anything else?
No response
BTY, If I install http-add-on without setting images.tag=canary
, everything works fine.
helm install http-add-on kedacore/keda-add-ons-http --create-namespace --namespace keda
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed due to inactivity.
i met the same issue, what's the solution for it?