Skip to content

Naming for resource is not following k8s pattern #13359

Open
@lukidzi

Description

@lukidzi

Description

As part of kumahq/kuma#3233, we agreed to follow Kubernetes-style resource naming conventions: zoneegress, meshproxypatch, etc. Unfortunately, our legacy resource uses the dash in the name: zone-ingress and global-secret. We should find a way to rename it by providing backward compatibility.

Metadata

Metadata

Assignees

Labels

kind/improvementImprovement on an existing featuretriage/acceptedThe issue was reviewed and is complete enough to start working on it

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions