April 17th, 2023 Community Meeting

[SaschaSchwarze0]

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

Rollout of SHIP-0036.

• Proposal: https://github.com/shipwright-io/community/pull/131
• We have two options on how to dynamically setup /etc/group and /etc/passwd in the container: https://github.com/SaschaSchwarze0/community/blob/sascha-0036-runas-user/ships/0036-runAs-for-supporting-steps.md#option-1-writable-files
  • Which one to take ?
• Sample implementation has been done for both options:
  • Option 1: https://github.com/shipwright-io/build/pull/1263 and https://github.com/shipwright-io/build/pull/1264
  • Option 2: https://github.com/shipwright-io/build/pull/1268 and https://github.com/shipwright-io/build/pull/1266

🐎

[qu1queee]

• Docker support for OS project, status.
• Ongoing v1beta1 migration
• Review on https://github.com/shipwright-io/cli/pull/180 (help wanted)
• CDF
  • https://devstats.cd.foundation
  • https://github.com/cdfoundation/wg-lfx-requirements
  • Possibility to have a new voting member in the TOC seat, as Shipwright Project representative
• CDCon 2023
  • We should have a blog post
  • Need of a release
  • Who is going?
  • Schedule Open Slots

🐖

[jitendar-singh]

Testing openshift build v2

Today the shipwright build controller project is strongly covered by e2e tests.These e2e tests are running on a kind cluster.

As part of Openshift Builds productization, we would like to ensure test coverage on openshift. We have identified two test approaches that we would like to discuss for productization.

Approach 1

Running existing upstream e2e tests on Openshift We will have to Configure openshift CI to run the test already present upstream.

needs discussion with the community to run tests on openshift CI against each PR OR fork upstream and do run the ci-bot on a downstream project under Openshift github organization needs test to be adapted(compatible with openshift as currently they run on KIND) Effort involved is unknown

Approach 2

Run QA test to Qualify releases based on artifact provided by CPaaS builds and brew

These are E2E tests to QA the whole chain: operator installation, build controller, Side image used by Openshift Builds like Git-clone, Image-bundler, and also specific Rbac for openshift Define a set of feature that need to be tested for the GA(Needs sync with Siamak Sadeghianfar) We already have a framework for it Use UMB to automate the triggering of test via CPaaS: this needs to set up an infrastructure for this CI (Other project like pipelines are using this approach)

Document Link : Testing openshift build v2

:shark:

[SaschaSchwarze0]

Docker Support for OS projects

• Would be nice to be recognized by Docker as open source community
• But no priority atm
• We probably have outdated things on quay, but never stored anything in DockerHub

Beta API

• Is ongoing, PR exists for proposal as well as the beta types
• By sticking with alpha on persistence, it is not so critical these days in case we make a mistake

CLI pull request to make it a kubectl plugin

• engage with new contributor in case help is needed

CDF updates

cdCon updates

• Present: Adam, Enrique, Matthias
• Release: broken is the operator (https://github.com/shipwright-io/operator/issues/113), triggers has no release ci yet

runAsUser

• Option 2 preferred, but also check the following:
• Instead of setting up /etc/passwd / /etc/group we can investigate in an alternative to using git at all. Problem originally was missing git-lfs support. Is that still the case for go-git or an alterative?
• Relevance of git-lfs: likely not used too much, but there is risk of taking features away
• securityContext with just runAsUser and runAsGroup on spec level

Testing on OpenShift

• longer discussions on test procedures and build strategy support

/close

[openshift-ci[bot]]

@SaschaSchwarze0: Closing this issue.

In response to [this](https://github.com/shipwright-io/community/issues/134#issuecomment-1511459604): >Docker Support for OS projects >* Would be nice to be recognized by Docker as open source community >* But no priority atm >* We probably have outdated things on quay, but never stored anything in DockerHub > >Beta API >* Is ongoing, PR exists for proposal as well as the beta types >* By sticking with alpha on persistence, it is not so critical these days in case we make a mistake > >CLI pull request to make it a kubectl plugin >* engage with new contributor in case help is needed > >CDF updates > >cdCon updates >* Present: Adam, Enrique, Matthias >* Release: broken is the operator (https://github.com/shipwright-io/operator/issues/113), triggers has no release ci yet > >runAsUser >* Option 2 preferred, but also check the following: >* Instead of setting up /etc/passwd / /etc/group we can investigate in an alternative to using git at all. Problem originally was missing git-lfs support. Is that still the case for go-git or an alterative? >* Relevance of git-lfs: likely not used too much, but there is risk of taking features away >* securityContext with just runAsUser and runAsGroup on spec level > >Testing on OpenShift >* longer discussions on test procedures and build strategy support > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.