Matt Richards
Matt Richards
Fresh install on a virtual machine fails with "Did not detect nodejs 8.x candidate for installation"
Looks like #103 may help. The advice from @sandaliero seems to have gotten me over the issue.
Fresh install on a virtual machine fails with "Did not detect nodejs 8.x candidate for installation"
Ah, too bad. I also was going from a fresh install but their troubleshooting steps did get me past that hurdle. Now I'm stuck with a new error trying to...
Fresh install on a virtual machine fails with "Did not detect nodejs 8.x candidate for installation"
I don't remember what the exact error was, but it seems like it actually was network issues on my side. Once I got those figured out everything installed perfectly. I'm...
Fresh install on a virtual machine fails with "Did not detect nodejs 8.x candidate for installation"
Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial Like you, it is installed on a VM (VMWare)
We also could use support for StatefulSet, as well as things like SealedSecrets, ClusterRoleBindings, Namespaces, etc. I know the argument is made that you only want to use this plugin...
I just ran into this issue as well, using Okta as OIDC Provider. The remediation steps of manually inputting the OIDC secret after ALB creation got me past it.