Search results

security: threat model

Status: Open.

#767 In Azure/aks-desktop;

· skoeva opened on Jul 14, 2026

aks desktop should point to its own plugin folder rather than headlamp folder

Status: Open.

#766 In Azure/aks-desktop;

· skoeva opened on Jul 14, 2026

create a path for organization-contributed plugins

Status: Open.

#765 In Azure/aks-desktop;

· skoeva opened on Jul 14, 2026

[BUG] Pods view does not show all provisioned pods (missing toggle/pagination) on macOS in AKS Desktop v0.7.0

bugSomething isn't workingSomething isn't working

triage

Status: Open.

#726 In Azure/aks-desktop;

· kasunsjc opened on Jun 14, 2026

WIP: 0.7.0 release notes

Status: Open.

#705 In Azure/aks-desktop;

· skoeva opened on Jun 1, 2026

[FEATURE] feedback / contact us link in tool

enhancementNew feature or requestNew feature or request

triage

Status: Open.

#679 In Azure/aks-desktop;

· danielsollondon opened on May 20, 2026

[FEATURE] banner for new releases

enhancementNew feature or requestNew feature or request

triage

Status: Open.

#678 In Azure/aks-desktop;

· danielsollondon opened on May 20, 2026

ossf security best practice: The project MUST have evidence that the [test_policy](https://www.bestpractices.dev/en/projects/11652/passing/edit#test_policy) for adding tests has been adhered to in the most recent major changes to the software produced by the project

Status: Open.

#676 In Azure/aks-desktop;

· illume opened on May 18, 2026

ossf security best practice: The release notes MUST identify every publicly known run-time vulnerability fixed in this release that already had a CVE assignment or similar when the release was created. This criterion may be marked as not applicable (N/A) if users typically cannot practically update the software themselves (e.g., as is often true for kernel updates). This criterion applies only to the project results, not to its dependencies. If there are no release notes or there have been no publicly known vulnerabilities, choose N/A.

Status: Open.

#675 In Azure/aks-desktop;

· illume opened on May 18, 2026

ossf security best practice: The project MUST provide, in each release, release notes that are a human-readable summary of major changes in that release to help users determine if they should upgrade and what the upgrade impact will be. The release notes MUST NOT be the raw output of a version control log (e.g., the "git log" command results are not release notes). Projects whose results are not intended for reuse in multiple locations (such as the software for a single website or service) AND employ continuous delivery MAY select "N/A".

Status: Open.

#674 In Azure/aks-desktop;

· illume opened on May 18, 2026

ossf security best practice: To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases

Status: Open.

#673 In Azure/aks-desktop;

· illume opened on May 18, 2026

ossf security best practice: Add reference documentation describing external interface The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project

Status: Open.

#672 In Azure/aks-desktop;

· illume opened on May 18, 2026