Unable to Deploy on v2.8.0 ontop of Digitalocean K8 Cluster

[davidchua]

Unable to Deploy on v2.8.0 ontop of Digitalocean K8 Cluster

[bacongobbler]

The builder follows the slugbuilder container's logs in order to display the build output similar to Heroku. What would be the expected output here in cases when the builder cannot fetch the logs from slugbuilder?

[bacongobbler]

If it's an upstream issue via kubernetes/kubernetes#33718 then personally I'm more prone to suggest upgrading to a release with that fix if there's no actionable items required otherwise. Anything we implement in Workflow will just be a workaround for this bug.

[davidchua]

The issue is that the deploy stops, and there's no pods created in the application namespace. Its as though a deploy didn't happen.

[bacongobbler]

That is intentional. If the builder cannot retrieve logs then it fails and backs out. If you feel up to it you can take a crack at a PR to work around the no such host issue, but it'd be a temporary thing until the upstream issue is resolved and a release is issued.

[bacongobbler]

Looks like the issue has been resolved upstream in 1.5.0-alpha.1, so there's nothing we need to do on our end. If you can test running Workflow on 1.5.0-beta.1 and confirm it works for you, then I think we can close this one out.

[bacongobbler]

I'm going to close this ticket due to inactivity, but please re-open if this still needs to be addressed. Thanks!