March 1st, 2021 Community Meeting

[qu1queee]

• 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 😸

[qu1queee]

• From @akram, BuildRun status should contain built image digest when the build is succesful
• Discuss how to proceed with Publish nightly releases #600. Nice initiative from @imjasonh .
• There was one topic we have been discussing internally around the difference between how a Dockerfile is resolved relative to its context directory. The behaviour between kaniko and docker is not the same. The first one looks always first in the root directory of the project, while docker always look first on the specified context directory.
  

[imjasonh]

Latest attempt at nightly releases at #626

[otaviof]

I would like to recap on the "remote artifacts" subject, the initial changes for this feature is at #616, open for early feedback.

[gabemontero]

a lesson from tekton on the required commitment of your api going from alpha to beta: https://kubernetes.slack.com/archives/C019ZRGUEJC/p1614018974009600

[qu1queee]

Meeting minutes:

• BuildRun status should contain built image digest when the build is succesful #618 is a good idea, we should also consider to provide the commit SHA together with the image digest.
• PR Take 2: Publish nightly release assets #626 is an improvement on the previous approach that reduces the amount of generated draft releases.
• We discussed the little differences on behaviour between Kaniko and Docker. For the time being we should consider adding an FAQ around this differences. Forcing Kaniko to behave like Docker via our strategies might have consequences in the future for users that are comfortable with the Kaniko particular behaviour.
• Remote Artifacts #616 ready for review. Support for multiple git repositories will be first tackle via an isolate EP, the current PR is not aiming to provide support for that.
• @gabemontero provided some nice findings on how Tekton have been dealing with the migration from alpha to beta, more details in March 1st, 2021 Community Meeting #619 (comment)
• @HeavyWombat is currently working on the last piece to remove dependencies to the operator-sdk, a PR will be provided soon around the refactoring for e2e tests.
• @adambkaplan request to have a grooming biweekly session, date and time to be confirmed.

[zhangtbj]

Finish and close this meeting minutes.