After applying the Traefik strip prefix configuration, it takes 2 to 3 hours for the change to take effect on the application

Traefik Traefik v2
1

My config:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: traefik-ingress
  namespace: argocd
spec:
  project: default
  source:
    repoURL: 'https://traefik.github.io/charts'
    chart: traefik
    targetRevision: 24.0.0
    helm:
      values: |-
        persistence:
          enabled: true
          size: {{ .Values.ingress.persistence.size }}
          storageClass: longhorn

        logs:
          general:
            level: DEBUG
          access:
            enabled: true
            format: json

        deployment:
          replicas: {{ .Values.ingress.replicaCount }}
          initContainers:
            - name: volume-permissions
              image: traefik:v2.10.4
              command:
                [
                  "sh",
                  "-c",
                  "touch /data/acme.json; chown 65532 /data/acme.json; chmod -v 600 /data/acme.json",
                ]
              securityContext:
                runAsNonRoot: false
                runAsGroup: 0
                runAsUser: 0
              volumeMounts:
                - name: data
                  mountPath: /data
        metrics:
          prometheus:
            addRoutersLabels: true
            addServicesLabels: true
            
        service:
          type: NodePort

        ports:
          web:
            nodePort: 32080
          websecure:
            nodePort: 32443
        ingressRoute:
          dashboard:
            enabled: false
  destination:
    server: https://kubernetes.default.svc
    namespace: traefik
  syncPolicy:
    automated:
      prune: true

When I try to use strip prefix for my applications, the changes take a very long time to reflect—usually around 2 to 3 hours. I restarted Traefik and cleared browser caches, but it didn’t help. As a last resort, I ended up using replace path instead. I'm wondering why strip prefix didn’t work as expected.I can see the applied strip prefixes appearing in the logs.

2

To me that sounds rather like an issue with your Kubernetes setup, updating the config.