Hi, > > I think most teams at the Brno F2F were struggling with this. It works > > locally, but semi-obscure failures when pushed 'live'. And out of the 30 RH > > engineers there, none knew 100% or was able to dig up a doc that explained > > why and how to fix it... > > > > This is/will be a massive pain point moving from Dev to Production. The > > very least we need some very clear, simple guides on how to make it work. > > Yeah, I think a lot of people are going to be very frustrated by this. > It took me over an hour to track down and that's only because I know a > lot about how the CDK is set up. Others would probably never be able > to figure it out.
It works the other way around as well as I painfully experienced and I think it took me more than an our to find out how to fix (aka be more permissive). All I could get from the logs etc were some seemingly unrelated Java stack traces. I think by now there are some better warnings at place, but still, it is a major pain point. When are you more likely to turn your back on the CDK? Right in the beginning when you cannot get anything to work or later down the road where you already put some time into it and have something running locally, but you cannot push it into a production environment. I am tempted to say the former. +1 to do everything we can from a documentation point of view. --Hardy
signature.asc
Description: PGP signature
_______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
