November 16th Community Meeting

[zhangtbj]

• Please add a topic in this thread and add a link to the Github issue associated with the topic.
• Please make sure you give folks enough time to review/discuss the topic offline on Github before coming into the meeting
• (optional) Paste the image of an animal smile

[qu1queee]

As mentioned in the last meeting, we would like to quickly discuss on particular cards just for everyone to have the full context. This should be a briefly discussion just to understand if there is something were we need to do a deep dive later.

release-v1.0.0:

• specify labels to be set on output images
• Pruning of BuildRun Objects
• Proxied Cluster Support and Sample build strategies should be secure by default
• New Build experience via CLI
• Support list of "env" variables in the Build spec
• Feature Request: Trigger builds on build definition changes

Post GA

• cancelling running/in flight BuildRun
• Image Change Triggers for build v2
• leverage tekton SCM trigger support
• inject source via image feature (something to be partially covered in @otaviof EP)
• inject source via config map / secrets feature
• image pull policy feature

[adambkaplan]

Email lists - we now have an email server! We need to agree appropriate email forums and one-way lists (for things like security issues and code of conduct violations).

[qu1queee]

Community meeting minutes:

• We mainly discuss some of the items belonging to release-v1.0.0 and Post GA. This was to provide context to everyone on what we have there and to get the brain of some folks (e.g. @gabemontero ) for more context on those cards.
• For Proxied Cluster Support #57, we might engage or look on what Tekton have. Also keep in mind that the more collaboration we can do in the Tekton side, the better.
• For Sample build strategies should be secure by default #169, we should consider the use case of the openshift local registry and a way to opt-out on the approach where security is required.
• For New Build experience via CLI #59 , we would like to have a quick 5min demo around oc, mainly for those ones that are not at all familiar.
• For image pull policy feature #46, we need to consider the use-case where particular tools( e.g. kaniko), have support a flag to configure the feature, so that the API field in Build can map to that tool flag.
• @adambkaplan shared on the email server that is now available for us, @adambkaplan anything you need from our side ?

Thanks all for joining!