Skip to content

Storage class check can prevent deployments where no storage class is needed for the registry #2273

@Racer159

Description

@Racer159

Environment

Device and OS: System76 darp8
App version: v0.32.2
Kubernetes distro being used: any (as long as they have no storage class)
Other: n/a

Steps to reproduce

  1. Create a cluster without a storage class
  2. Deploy the Zarf init package with an S3 or ephemeral registry

Expected result

Zarf successfully deploys

Actual Result

Zarf will fail with stating that it cannot find a storage class

Severity/Priority

Medium

Additional Context

There are work arounds with custom init packages but this use case should be handled since it is a regression from what the default Zarf init package used to be able to do.

Metadata

Metadata

Assignees

Labels

bug 🐞Something isn't workingneeds-investigationFor triage issues that need more research.

Type

No type

Projects

Status

Ready

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions