brigadecore / go-tools

A curated set of containerized Go tools to facilitate Brigade development

Brigade Go Tools Image

This project provides a curated set of containerized Go tools to facilitate development of Brigade and several related projects.

Contributing

The Brigade project accepts contributions via GitHub pull requests. The Contributing document outlines the process to help get your contribution accepted.

Support & Feedback

We have a slack channel! Kubernetes/#brigade Feel free to join for any support questions or feedback, we are happy to help. To report an issue or to request a feature open an issue here.

Code of Conduct

Participation in the Brigade project is governed by the CNCF Code of Conduct.

go-tools's Issues

Add slack badge to README.md

See brigadecore/brigade#1716

This repo requires the same change.

Docker image for Arm64 platform is required

Hi Team,
I am trying to use the go-tools image on arm64 platform but it seems it is not available for arm64.
I have successfully built the image using the command docker build -t <image_name> . on the arm64 platform with no change.
Do you have any plans on releasing arm64 image?
I've successfully pushed the image on my dockerhub using Travis-CI. May I know how the amd64 image is getting published on Dockerhub?
If interested, I will raise a PR.

Scan images, generate SBOMs, sign images

For Brigade itself and all its peripherals, we're now scanning images for vulnerabilities as part of CI, generating and publishing SBOMs as part of the release process, and also signing our images.

Now that that's been attended to, it's time to move the security conversation farther back in our stack and apply those learnings to the images we regard as tools or a means to an end.

This issue calls for scanning images during CI, generating and publishing SBOMs during release, and signing images.

The pattern for these things is well established by now and I think can reasonably be handled in a single PR.