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.

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

Add custom CA support for buildkit/pro-builder #1229

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

alexellis
Copy link
Member

These are breaking changes to allow easier management of the images, and root/rootless settings.

Description

Add custom CA support for buildkit/pro-builder

Why is this needed?

For use with an in-cluster or self-signed registry such as Habor, or "distribution" aka Docker's OSS registry

Who is this for?

Requested by a customer

How Has This Been Tested?

Deployed a self-hosted registry with distribution, with a generated CA, and cert signed by the CA. The CA was given to buildkit, and faas-cli publish --remote-builder.

The image was published successfully with the rootless and root mode.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

An overdue breaking change is made along with the custom CA support, in order to make it easier to update the images for root/rootless, and to avoid having to comment out blocks.

Users will now set mode: [root|rootless] rather than buildkit.rootless: true/false

Checklist:

There will be an update to the Helm chart README and the docs to mention the new custom CA support.

These are breaking changes to allow easier management of the
images, and root/rootless settings.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant