Ben Parees
Ben Parees
+1. an env variable isn't a terrible idea, but just making the default image behavior "correct" seems like a better experience.
@hhorak @pkubatrh @praiskup bump
what happens in the back-pressure case? the logs continue to accumulate in the pipe/buffer indefinitely(Assuming the log rate never drops)? can this cause memory consumption issues? who's memory budget does...
> so it'd be charged to the pod that sounds like the right place for it, so that's good.
> Streaming the build context to the Pod is (probably?) going to be secure if proxied by the API server, which creates unnecessary API Server load (I believe the OpenShift...
> @bparees it's not completely clear to me how folks typically use Binary? Basically they typically use it when they have local source (either no git repo or they don't...
> I am curious what storage medium you use to transmit the file? we stream it directly from the client machine to the running pod (might go through the api...
@mattmoor yeah i think it's useful. it's a concept we've wanted to add to openshift builds for a while, basically two things have kept us from doing it: 1) if...
> However, this doesn't trigger a ConfigChange in either DeploymentConfig because the environment variables are secret references (it seems like this would be the obvious thing to do). obvious, perhaps,...
needs to test the template w/ both the centos and rhel image.