Skip to content

Lowercase RFC 1123 in IngressRoute name #1732

@BirkelbachToni

Description

@BirkelbachToni

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?

39.0.5

What version of Traefik are you using?

v3.6.10

What did you expect to happen ?

I wanted to roll out traefik on my Kubernetes cluster with ArgoCD

What did you notice instead ?

Error

Sync operation to failed: one or more objects failed to apply, reason: IngressRoute.traefik.io "traefik-kubernetesCRD" is invalid: [metadata.name: Invalid value: "traefik-kubernetesCRD": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), spec.routes[0].match: Required value],IngressRoute.traefik.io "traefik-kubernetesIngress" is invalid: [metadata.name: Invalid value: "traefik-kubernetesIngress": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), spec.routes[0].match: Required value]


Cause

The Problem is that the trafik templates uses this Syntax to generate their names:

name: {{ $.Release.Name }}-{{ $name }}

The Problem accures when referencing these two lines in the values

kubernetesCRD:

kubernetesIngress:

(I'm sure there are more, but I only have these two troublemaker enabled)

It simply copies the name with uppercase letters wich don't match with the lowercase RFC 1123 syntax rules.

My Kubernetes-Client-Version is v1.34.1

What are your values ?

ingressRoute.kubernetesCRD.enabled = true
ingressRoute.kubernetesIngress = true

Additional Information

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomershelp wantedPRs are welcome on this issuekind/bug/possiblea possible bug that needs analysis before it is confirmed or fixed.

    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