#v0.9.0 SDK workflows in AKS with v0.0.2 dagger-engine Helm Chart

1 messages · Page 1 of 1 (latest)

tight pivot
#

I have functioning v0.8.7 SDK workflows executing in ARC provisioned GH runners in AKS -- But my v0.9.0 SDK workflows are failing with:

Creating new Engine session... OK!
Establishing connection to Engine... 1: connect
1: > in init
1: starting engine 
1: starting engine [0.02s]
1: connect ERROR: new client: remote is not a valid dagger server (expected "github.com/dagger/dagger", got "dagger-dagger-helm-engine-b8jtl")
Error: new client: remote is not a valid dagger server (expected "github.com/dagger/dagger", got "dagger-dagger-helm-engine-b8jtl")
panic: EOF: 1: connect
1: > in init
1: starting engine 
1: starting engine [0.02s]
1: connect ERROR: new client: remote is not a valid dagger server (expected "github.com/dagger/dagger", got "dagger-dagger-helm-engine-b8jtl")
Error: new client: remote is not a valid dagger server (expected "github.com/dagger/dagger", got "dagger-dagger-helm-engine-b8jtl")


goroutine 1 [running]:
main.main()
    /runner/_work/workflows/workflows/ci/src/main.go:52 +0x17d```

It looks like the DaemonSet name is not matching the expected name. Are updates to the Helm Chart required?