IP Certificate Ignored in Favor of Auto-Generated Certificate in a k3s Environment

General Discussions
1

I have a server set up with k3s, and everything is currently using the default settings from a fresh installation. However, I want to access the server via its IP address using HTTPS, rather than using a domain name. I have an IP certificate for the server’s address, and I’ve created a ‘whoami’ example for accessing it through an IngressRoute. There are a few situations:

  1. Everything works fine when accessing via HTTP.
  2. When accessing via HTTPS, it doesn’t use my own IP certificate but instead uses a certificate automatically generated by Traefik.
  3. Everything works fine when I switch to using a domain name and a domain certificate.

Can you help me understand where the problem might be?

apiVersion: v1
kind: Service
metadata:
  name: whoami
  namespace: default
spec:
  ports:
    - protocol: TCP
      name: web
      port: 80
  selector:
    app: whoami
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: whoami
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: whoami
  template:
    metadata:
      labels:
        app: whoami
    spec:
      containers:
        - name: whoami
          image: containous/whoami
          ports:
            - name: web
              containerPort: 80
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: whoami
  namespace: default
spec:
  ingressClassName: nginx
  rules:
  - match: Host(`*.*.*.*`) && PathPrefix(`/`)
    kind: Rule
    services:
    - name: whoami
      port: 80
  tls:
      secretName: ip-tls