Optional signing for pull/push and baseProfileName

[MaksimKlepikov]

My use case:

1. Collect seccomp profiles using SPO
2. Put these profiles as json files in Gitlab project
3. In Gitlab CI/CD pipeline push profiles as oci artifcats to Gitlab registry
4. Specify result oci profiles in SeccompProfile

The Gitlab itself is self-hosted in air-gapped environment.

The problem is in step 3, where spoc tries to sign it in non-interactive mode and also in air-gapped environment (even if https_proxy configured), so it fails with an error.

It would be nice to add documentation on how to use it in an air-gapped environment, or make signing optional.

[ccojocar]

I am not sure if skipping the signing is a good idea. I think you need to allow https://oauth2.sigstore.dev domain. Maybe making the OIDC provider configurable.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale