Skip to content

Conversation

@humoflife
Copy link
Contributor

Description

  • Explain how to use imageConfig to only pull authorized images and essentially implement a lean and clean way of marketplace repo segregation

Type of change

  • Bug fix (typo, broken link, incorrect info)
  • Content update (new info, clarification, reorganization)
  • New content (new page, section, or guide)

Checklist

  • I ran make lint locally (or will fix Vale suggestions in review)
  • Links work and point to the right places
  • If this adds new content, I tested the examples/instructions

Additional notes

@vercel
Copy link

vercel bot commented Dec 12, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Dec 12, 2025 4:33pm

Signed-off-by: humoflife <markus.schweig@upbound.io>
like below.

```
kubectl describe imageconfigs.pkg.crossplane.io
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use Here a get .... -o yaml ? It's hard to Copy when using s describe

## Benefits

- Developers can push artifacts to one or more [marketplace][marketplace] registries, including a third party enterprise locations, and production control planes can only successfully consume the signed image versions.
- Signing can happen in place for the images that pass CI/CD pipeline tests.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how does this work for Projects ? I know how this works fot Upbound official providers but wonder what folks need To-Do in CI when pushing the Project - can we Show the signing CI step too ?

Signed-off-by: rae sharp <8883519+tr0njavolta@users.noreply.github.com>
Updated the guide to clarify repository access segregation and image signing processes, improving readability and conciseness.

Signed-off-by: rae sharp <8883519+tr0njavolta@users.noreply.github.com>
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.

4 participants