Charles Moulliard

> it would still be this "magic" step This is the reason why I think that the best approach then will be for the developers to propose something like this:...

> Not sure. Wouldn't this mean that the developer API is another, smaller set of YAML configuration that then gets processed by the controller, translated into a broader set of...

> When I say "magic", what I mean are of course things like: > > * In the resulting YAMLs, there's multiple places where you have to put parameter X...

My 5cents idea of the day ;-) to at least improve the situation Why dont you package the needed cf/kubernetes tools such as: `ytt, kapp, kpack, bosh, cf, ...` within...

Is it fixed ? @LalatenduMohanty

I can reproduce it locally using this config ``` minishift v1.20.0+53c500a - cpus : 4 - image-caching : false - iso-url : centos - memory : 4G - openshift-version :...

> can you remove the changeset? Done

I think that it is time to bump the Platform version to at least 0.10 otherwise we got this error ``` buildpack API version '0.7' is incompatible with the lifecycle...

There is a workaround which is to use as registry hostname `*.local`. In this case the go-containerregistry lib used by lifecycle will issue a HTTP call instead of a HTTPS...

If I do `./minishift_virtualbox.sh stop` followed by `./minishift_virtualbox.sh start`, then the same error is reported ``` ssh [email protected] [email protected]'s password: Last login: Thu Jan 24 15:57:06 2019 from 192.168.99.1 Red...