Skip to content

Extra space in tridentactionmirrorupdates CRD YAML template indentation #1120

@JRuumis

Description

@JRuumis

Description:
There is an extra leading space in the indentation of the following YAML template:
https://github.com/NetApp/trident/blob/master/cli/k8s_client/yaml_factory.go#L2301-L2358

System Impact & Context:

  • The Pipeline Constraint: Our deployment orchestrator forces CRDs into the Helm templates directory rather than the standard crds folder.
  • The Parsing Failure: Helm's template parser enforces significantly stricter YAML formatting than native Kubernetes CRD application.
  • The Bottleneck: This strictness causes the single-space offset to fail the Helm deployment, and we lack an easy workaround to bypass the orchestrator's directory logic.

Removing this extra space is a trivial structural fix. It ensures broader compatibility for downstream users with custom or strict Helm deployment architectures.

Note: I'm afraid we have jumped the gun with issue and already created a pull request for the change: #1119

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions