Skip to content

Breaking: Instance labels and selector labels need to be standardized #553

@krumware

Description

@krumware

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Currently the labels on the deployment workloads and services workloads are hardcoded, and do not leverage the release name. This could cause issues with multitenancy and is not standard for modern helm charts.

Expected Behavior

These labels should be updated, but this may force an upgrade workflow through specific versions, or redeployment of epinio instances.

Steps To Reproduce

No response

Environment

- OS:
- Architecture:
- Epinio Version:
- Cluster:
  - Provider:
  - Options:
  - Kubernetes Version:

Logs

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions