AFAICT you cant configure the operator to explicit...
# pulumi-kubernetes-operatorp
prehistoric-kite-30979
09/15/2021, 1:26 PMAFAICT you cant configure the operator to explicitly use yarn over npm. Will the operator autodetect yarn?
s
sparse-park-68967
09/15/2021, 10:11 PMYes you are right. Could you open an issue in https://github.com/pulumi/pulumi-kubernetes-operator/issues please?
p
prehistoric-kite-30979
09/16/2021, 12:47 PMSo will it automatically use yarn if it detects a
yarn.locks
sparse-park-68967
09/16/2021, 4:55 PMThat seems like a reasonable approach. Would also be nice to take a stack configuration override to force one over the other.
sparse-park-68967
09/16/2021, 5:00 PMAs a quick/hacky workaround, you could potentially install an init container which deletes the npm binary from the image - we currently first look for npm and then fallback to yarn. Both are installed in the image so always choose npm.. https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/pkg/controller/stack/stack_controller.go#L729
p
prehistoric-kite-30979
09/16/2021, 10:49 PMdoing that check wouldn’t actually solve my problem as I’m using yarn workspaces… I’ll do the init workaround
prehistoric-kite-30979
09/16/2021, 10:54 PMprehistoric-kite-30979
09/16/2021, 10:54 PMI’ve added that comment about yarn.lock as well
prehistoric-kite-30979
09/27/2021, 9:41 PMI’ve also added the dockerfile we use to workaround this.