Skip to content

[TRACKING] Assess kustomize patch targets #278

Description

@vitorfloriano

Summary / Objective

It seems that some patches are being targeted too broadly.

Targeting too broadly could cause unintended side-effects (see #276) and lead to misconfigs.

We should assess if the current kustomize patch targets could be narrowed to avoid such issues.

Checklist / Sub-tasks

  • Narrow the scope of kustomize patch targets to avoid side-effects
  • Add tests to ensure configuration in manifests is sane

Design Documents & References

No response

Target Milestone / Release

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/community-meetingIssues or PRs that should potentially be discussed in a Kubernetes community meeting.priority/backlogHigher priority than priority/awaiting-more-evidence.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions