Allow associating a chart with a container image via OCI Referrers API.
When pushing a chart with --subject, the manifest will include a subject
field pointing to the specified digest.
Example: helm push chart.tgz oci://registry/repo --subject sha256:abc...
This enables workflows where Helm charts are published as referrers
to container images, allowing registry clients to discover related
artifacts through the OCI Referrers API.
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Per HIP-9999 and OCI Image Spec 1.1, set artifactType field in manifest
to enable efficient artifact selection from OCI Image Index.
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
When helm pull encounters an OCI Image Index containing multiple
manifests, it now selects the appropriate Helm chart manifest by
checking the artifactType field (OCI 1.1) or falling back to
config.mediaType inspection.
This enables publishing both container images and Helm charts under
the same OCI tag, similar to how multi-arch images work.
Selection logic:
1. First, check for explicit artifactType match in Index descriptors
2. If no match, fetch manifests without platform and check config.mediaType
3. Skip manifests with platform selector (likely container images)
Closes: https://github.com/helm/helm/issues/31582
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
The rangeint suggestion is faster.
The maps.Copy and slices.Contains are just syntatic sugar.
Signed-off-by: Mads Jensen <atombrella@users.noreply.github.com>
The kube client logging is based on the actionConfig logging. This
is setup to use slog.Default() before the logging flags are parsed
and logging is setup.
newRootCmdWithConfig changes the logging but it wasn't picked up
for actionConfig or the kube client. This change updates the logging
to include any changes.
Signed-off-by: Matt Farina <matt.farina@suse.com>
Adds chart name to dependency logs, namespace to resource waiting logs,
and confirmation message when all resources are ready.
Addresses #31520
Signed-off-by: shuv0id <110290476+shuv0id@users.noreply.github.com>
While testing SDK features for v4. I was surprised with the error:
"reporter failed to start: event funnel closed: context deadline exceeded"
This occurs when no timeout is set:
```
upgradeClient := action.NewUpgrade(actionConfig)
upgradeClient.WaitStrategy = kube.StatusWatcherStrategy
// When Timeout is zero, the status wait uses a context with zero timeout which
// immediately expires causing "context deadline exceeded" errors.
upgradeClient.Timeout = 2 * time.Minute
```
With this patch it will work without specifying.
Signed-off-by: Benoit Tigeot <benoit.tigeot@lifen.fr>
> "reporter failed to start: event funnel closed: context deadline exceeded"
It happens when you forget to set a minimal timeout:
```go
upgradeClient := action.NewUpgrade(actionConfig)
upgradeClient.WaitStrategy = kube.StatusWatcherStrategy
// When Timeout is zero, the status wait uses a context with zero timeout which
// immediately expires causing "context deadline exceeded" errors.
upgradeClient.Timeout = 2 * time.Minute
```
Also maybe it might be worth documenting this more clearly. Initial [PR](https://github.com/helm/helm/pull/13604) say:
> I have not written any docs, I assume that can be done when we are closer to Helm 4, a lot of it is covered by linking to - https://github.com/kubernetes-sigs/cli-utils/blob/master/pkg/kstatus/README.md
Related:
- https://github.com/helm/helm/pull/31411#issuecomment-3443925663
Signed-off-by: Benoit Tigeot <benoit.tigeot@lifen.fr>
LoadArchive is in the individual loaders for the chart versions.
It is used by SDK users to load a stream rather than a file on
the filesystem. Adding to support SDK users like Flux.
Signed-off-by: Matt Farina <matt.farina@suse.com>
Aleksei Sviridkin
Matt Farina
George Jenkins
megha1906
Robert Sirchia
Mads Jensen
Benoit Tigeot
shuv0id
Terry Howe
Scott Rigby
promalert
Benoit Tigeot
saimanojk1
tison