Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

June 17th, 2024 Community Meeting #210

Closed
qu1queee opened this issue Jun 17, 2024 · 4 comments
Closed

June 17th, 2024 Community Meeting #210

qu1queee opened this issue Jun 17, 2024 · 4 comments
Labels
community meeting

Comments

@qu1queee
Copy link
Contributor

  • 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
Copy link
Member

I suggest to remove that kaniko+trivy build strategy now that vulnerability scans are a first-class capability. Any objections ?

@HeavyWombat
Copy link
Contributor

Found this weird behavior: shipwright-io/build#1621

@adambkaplan
Copy link
Member

Status update for operator v0.13.0 - needs shipwright-io/operator#218

@qu1queee
Copy link
Contributor Author

Meeting minutes:

  • Yes to comment.
  • Discussion on the way we write tests, with or without ginkgo.
  • Close to ship v0.13.0 for the Operator.

@SaschaSchwarze0 SaschaSchwarze0 mentioned this issue Jun 21, 2024
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
community meeting
Projects
Shipwright Overview
Status: Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@adambkaplan @HeavyWombat @qu1queee @SaschaSchwarze0