May 15th, 2023 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 😸

[SaschaSchwarze0]

The runAs configuration item is becoming pressing:

• SHIP-0036: Proposal to set runAs user/group for supporting steps to the runAs configuration of the build strategy steps #131
• SHIP-0036: Part 1: Update base images to allow an arbitrary user to run it #1268
• SHIP-0036: Part 2: Update runtime logic to use a common runAsUser and runAsGroup in the steps when possible #1266

[otaviof]

🐅 Shipwright no OpenShift:

• OpenShift GA requires v1beta1 resources
• allow UI Team to start working on the changes from v1alpha1
• getting started on the admission webhook

[SaschaSchwarze0]

Conference updates ?

• Tekton artefacts
• CDEvents
  • produce events: Feature proposal: generate CDEvents for Shipwright #72
  • consume event as a trigger for a BuildRun
• Integrating Builds into Pipelines

runAsUser/group ship and code can be reviewed

RedHat is working on replacement for git-task for OpenShift Pipelines: https://github.com/openshift-pipelines/task-git

Beta API

• Rollout plan: https://github.com/shipwright-io/build/issues?q=is%3Aissue+is%3Aopen+%22BETA+API%22+
• Currently: beta endpoints not served because no conversion webhook exists to tranform them to alpha, and no controller reads the beta objects
• Goal for v0.12: have conversion webhook in place
  • Alpha would work like today
  • Users that create beta objects will get it converted by the webhook so that the controller can work on it in the alpha version, user can retrieve beta which will involve the conversion webhook again to convert alpha to beta
• Goal for v0.13: controller is reconciling on beta API, stored version is beta; conversion webhook only used when somebody still accesses alpha

Operator API

• Is also Alpha, https://github.com/shipwright-io/operator/blob/main/api/v1alpha1/shipwrightbuild_types.go
• Should we just change it to Beta assuming it is not known to be adopted anyway ? Or do we need to do the same like for the Build run time objects with conversion webhook etc?

/close

[openshift-ci]

@SaschaSchwarze0: Closing this issue.

In response to this:

Conference updates ?

• Tekton artefacts
• CDEvents
• produce events: Feature proposal: generate CDEvents for Shipwright #72
• consume event as a trigger for a BuildRun
• Integrating Builds into Pipelines

runAsUser/group ship and code can be reviewed

RedHat is working on replacement for git-task for OpenShift Pipelines: https://github.com/openshift-pipelines/task-git

Beta API

• Rollout plan: https://github.com/shipwright-io/build/issues?q=is%3Aissue+is%3Aopen+%22BETA+API%22+
• Currently: beta endpoints not served because no conversion webhook exists to tranform them to alpha, and no controller reads the beta objects
• Goal for v0.12: have conversion webhook in place
• Alpha would work like today
• Users that create beta objects will get it converted by the webhook so that the controller can work on it in the alpha version, user can retrieve beta which will involve the conversion webhook again to convert alpha to beta
• Goal for v0.13: controller is reconciling on beta API, stored version is beta; conversion webhook only used when somebody still accesses alpha

Operator API

• Is also Alpha, https://github.com/shipwright-io/operator/blob/main/api/v1alpha1/shipwrightbuild_types.go
• Should we just change it to Beta assuming it is not known to be adopted anyway ? Or do we need to do the same like for the Build run time objects with conversion webhook etc?

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.