Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning when ExternalName service loading is enabled #10676

Closed
2 tasks done
morremeyer opened this issue May 2, 2024 · 2 comments · Fixed by #10682
Closed
2 tasks done

Warning when ExternalName service loading is enabled #10676

morremeyer opened this issue May 2, 2024 · 2 comments · Fixed by #10682
Labels
area/provider/k8s/crd contributor/wanted Participation from an external contributor is highly requested kind/enhancement a new or improved feature. priority/P3 maybe
Milestone

Comments

@morremeyer
Copy link

morremeyer commented May 2, 2024

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 did you do?

Start traefik v3.0.0 with the option

--providers.kubernetescrd.allowExternalNameServices=true

I expected this to not have any effects besides allowing the use of ExternalName services.

What did you see instead?

There is a log with level warning about ExternalName services being enabled.

2024-05-02T10:04:22Z WRN ExternalName service loading is enabled, please ensure that this is expected (see AllowExternalNameServices option) providerName=kubernetescrd

Since ExternalName service loading is enabled because I explicitly configured it, I expect this to not print a log message of level warning, at most the level should be INFO in my opinion.

I'd expect a warning level log message to tell me about something that is wrong, not about me having configured an option.

What version of Traefik are you using?

v3.0.0

What is your environment & configuration?

Using the helm chart in v28.0.0 with the following values:

updateStrategy:
  rollingUpdate:
    maxUnavailable: 1

globalArguments: ~

providers:
  kubernetesCRD:
    allowExternalNameServices: true

additionalArguments:
  - --serverstransport.insecureskipverify
  - --certificatesresolvers.cloudflare.acme.dnschallenge.provider=cloudflare
  - --certificatesresolvers.cloudflare.acme.email=REDACTED_EMAIL
  - --certificatesresolvers.cloudflare.acme.storage=/data/acme.json
  - --metrics.prometheus=true
  - --providers.kubernetesingress.ingressclass=traefik
  - --providers.kubernetesingress.ingressendpoint.ip=REDACTED_IP
  
logs:
  general:
    level: WARN
  access:
    enabled: true

service:
  enabled: false

ports:
  web:
    hostPort: 80
    redirectTo:
      port: websecure
  websecure:
    hostPort: 443
    tls:
      enabled: true
      certResolver: cloudflare
      domains:
        - main: redacted.example.com
          sans:
            - "*.redacted.example.com"
  
ingressClass:
  enabled: true

env:
  - name: CLOUDFLARE_DNS_API_TOKEN
    valueFrom:
      secretKeyRef:
        name: cloudflare-token
        key: CLOUDFLARE_DNS_API_TOKEN

persistence:
  enabled: true

If applicable, please paste the log output in DEBUG level

No response

@nmengin
Copy link
Contributor

nmengin commented May 2, 2024

Hey @morremeyer,

Thanks for your suggestion, we think it makes sense.
Unfortunately, we are focused elsewhere. If you or another community member would like to build it, let us know.

Don’t forget to check out the contributor docs and to link the PR to this issue.

@nmengin nmengin added kind/enhancement a new or improved feature. priority/P3 maybe area/provider/k8s/crd contributor/wanted Participation from an external contributor is highly requested and removed status/0-needs-triage labels May 2, 2024
@marcmognol
Copy link
Contributor

Hi @nmengin,

I can contribute on it.
Marc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/k8s/crd contributor/wanted Participation from an external contributor is highly requested kind/enhancement a new or improved feature. priority/P3 maybe
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants