How to create an Ingress on a fresh install of k3s with Traefik

I say fresh, but I insatlled k3s in August and just now am getting around to using it. Anyways…I wanted to expose my Pod and Service I have that I was both able to connect to via Port-Forward and verify that they were working. So all I’ve done so far was deploy a Pod, and a Service. Now I wanted to create an Ingress like I do on other Kubernetes instaces I’ve worked with. however, that’s not so straight forward since we’re using Traefik 2.8.3 which uses IngressRoutes CRD. I’ve got the following IngressRoute manifest defined.

---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: foundryvtt-ingress-route
spec:
  entryPoints:
    - web
  routes:
    - kind: Rule
      match: Host(`filbot.net`) && Path(`/`)
      services:
        - name: foundryvtt-service
          port: 80
...

I see the IngressRoute when I view the cluster with k9s or kubectl. However, when I attempt to hit my node, I get 504 Gateway Timeout and I’m not sure why. Traefik also doesn’t seem to be able to see my Service I have defined. Resource Manifests are below.

These are the errors I continually get in the kube-system/traefik Pod.

W1023 05:22:17.587939       1 warnings.go:70] networking.k8s.io/v1beta1 IngressClass is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 IngressClassList                                                              
W1023 05:24:38.485776       1 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress                                                                                   
W1023 05:30:28.488751       1 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress                                                                                   
W1023 05:31:31.592034       1 warnings.go:70] networking.k8s.io/v1beta1 IngressClass is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 IngressClassList                                                              
time="2021-10-23T05:36:47Z" level=error msg="kubernetes service not found: default/foundryvtt-service" ingress=foundryvtt-ingress-route namespace=default providerName=kubernetescrd                                                        
time="2021-10-23T05:36:47Z" level=error msg="kubernetes service not found: default/foundryvtt-service" providerName=kubernetescrd ingress=foundryvtt-ingress-route namespace=default                                                        
time="2021-10-23T05:36:59Z" level=error msg="subset not found for default/foundryvtt-service" namespace=default providerName=kubernetescrd ingress=foundryvtt-ingress-route                                                                 
time="2021-10-23T05:37:00Z" level=error msg="subset not found for default/foundryvtt-service" namespace=default providerName=kubernetescrd ingress=foundryvtt-ingress-route                                                                 
time="2021-10-23T05:37:02Z" level=error msg="subset not found for default/foundryvtt-service" namespace=default providerName=kubernetescrd ingress=foundryvtt-ingress-route

Would anyone be able to help me figure out why Traefik isn’t seemingly allowing me to connect to my services or find it? Am I doing this correctly, or am I missing anything?

Same issue I am facing after updating k8s to newer version.

Any solution on this error?