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

Image Integrity on AKS #688

Open
marty2bell opened this issue Oct 11, 2018 · 29 comments
Open

Image Integrity on AKS #688

marty2bell opened this issue Oct 11, 2018 · 29 comments
Assignees
Labels
action-required azure/acr Azure Container Registry feature-request Requested Features security

Comments

@marty2bell
Copy link

Is this a BUG REPORT or FEATURE REQUEST?:
Feature

What happened?:
Content Trust has been released in preview for ACR, but I can't see anywhere were we can enable content trust within AKS as a consumer of the ACR?

What did you expect to happen?:
Pull docker images with content trust enabled

How do you reproduce it (as minimally and precisely as possible)?:

Anything else we need to know?:

Environment (if applicable to the issue):

@timwebster9
Copy link

👍 to this. I've asked this exact same question in Azure Advisors, and it's been viewed over 50 times with no answers :-).

@jluk jluk added the roadmap label Apr 3, 2019
@jluk
Copy link
Contributor

jluk commented Apr 3, 2019

This is on the roadmap, the proposal being that for AKS node pools you can define if a specific node pool should enforce content trust. This would apply for all nodes within the node pool.

@sujitdmello
Copy link

Any update on this? Is it still on the roadmap?

@jluk
Copy link
Contributor

jluk commented Jun 19, 2019

Ack, still on roadmap but we're prioritizing features such as SLB support and GA quality for VMSS clusters, multiple node pools, cluster autoscaler.

@jluk jluk self-assigned this Aug 9, 2019
@PedroAndrade89
Copy link

PedroAndrade89 commented Dec 2, 2019

Is there any progress on this?

@jluk
Copy link
Contributor

jluk commented Dec 3, 2019

Hi Pedro, not yet but acknowledging this is still under review on roadmap. Thanks for your patience on this and we will keep the latest updates on this issue.

@jluk jluk added feature-request Requested Features and removed roadmap labels Dec 3, 2019
@lgmorand
Copy link

lgmorand commented Dec 5, 2019

I do confirm that I have customers asking for it. I do hope, it will be back on the roadmap very soon

@ThorstenHans
Copy link

Is there any update regarding this one? I'm also working with a customer who wants to use ACR content trust from within AKS

@pplavetzki
Copy link

I also have a large client that wants to use signed ACR images with AKS.

@Smushatron
Copy link

Any update on this, we have two clients that wish to use this feature.

@flamingboo
Copy link

I have clients waiting on this feature for some time now. How far is it in AKS roadmap?
Any update?

@jluk jluk assigned sauryadas and unassigned jluk Feb 19, 2020
@enesunal
Copy link

enesunal commented Mar 12, 2020

Any updates?

@ezYakaEagle442
Copy link

I do confirm that I have customers asking for it. @jluk could you please update this issue ?

@sauryadas sauryadas assigned TomGeske and unassigned sauryadas Mar 31, 2020
@TomGeske
Copy link

TomGeske commented Apr 1, 2020

Any updates?
We are investigating the content trust scenario right now. Once we are ready to share more details, I will come back and update this GH issue.

@mnadeaugenetec
Copy link

Any updates ? we need this functionnality

@jluk
Copy link
Contributor

jluk commented Apr 28, 2020

This feature is ongoing for design and discussion.

A critical aspect for this feature on AKS is enabling a solution which can satisfy all requirements such as content moving repos or across registries which may extend beyond the current scope of the ACR content trust feature as seen today.

An important discussion on this front is ongoing with Notaryv2 and I would encourage following up on that workstream to see latest updates to progressing to an AKS solution.

https://github.com/notaryproject/requirements/blob/26143591574b214342b31ef276c7aa84942b1b7d/scenarios.md

@jluk jluk changed the title Enable AKS to use ACR with Content Trust Enabled Enable AKS to use ACR with an image signing solution (ex: Notaryv2, Content Trust) Apr 28, 2020
@jluk jluk added azure/acr Azure Container Registry feature and removed feature-request Requested Features labels May 5, 2020
@miwithro
Copy link
Contributor

miwithro commented Dec 3, 2021

ORAS Artifact support now enabled in South Central US: supply chain artifacts.

You can use notary Alpha 1 today. We're working on an end to end doc for how to use Notary v2 with Azure KeyVault, AKS and the Ratify project for signature validation, This will still be early preview, enabling users to engage for feedback.

@ghost ghost added the action-required label Jun 1, 2022
@ghost ghost removed the action-required label Aug 17, 2022
@wangyira wangyira reopened this Sep 21, 2022
@ghost ghost closed this as completed Sep 28, 2022
@wangyira wangyira reopened this Sep 28, 2022
@miwithro miwithro changed the title Enable AKS to use ACR with an image signing solution (ex: Notaryv2, Content Trust) Image Integrity on AKS Nov 22, 2022
@miwithro
Copy link
Contributor

Leveraging OPA/Gatekeeper, ACR w/Ratify and Notation, AKV, and AKS to create and end to end signing/verification solution for AKS customers.

@charleswool
Copy link
Contributor

We are targeting end of Sep to public preview Image Integrity

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action-required azure/acr Azure Container Registry feature-request Requested Features security
Projects
Status: Public Preview (Shipped & Improving)
Development

No branches or pull requests