Dynamic status page not showing via Traefik #165
Comments
|
Looking at the docs here: https://acouvreur.github.io/sablier/#/guides/code-server-traefik-kubernetes It shows using Traefik plugin version Also it shows using docker container |
Yes, you're right about that. The last action did not trigger the releases on tagging, I have to fix that by force publishing myself, I will do it soon. |
For your issue here, I'd be curious about your Traefik setup, can you please share more of the Traefik setup itself? With Sablier, the service you try to setup for scale to zero and Traefik itself? Thanks |
acouvreur
added
traefik
|
Hi, Here's the Traefik config: apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
name: sablier
namespace: test
spec:
plugin:
sablier:
group: test
sablierUrl: 'http://sablier.sablier.svc.cluster.local:10000'
sessionDuration: 30s
dynamic:
displayName: 'test'
showDetails: true
theme: hacker-terminal
refreshFrequency: 5s
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
name: test
namespace: test
spec:
entryPoints:
- https-external
tls:
secretName: external-tls
routes:
- kind: Rule
match: Host(`test.test.com`) && PathPrefix(`/test/v1`)
middlewares:
- name: sablier
namespace: test
services:
- kind: Service
name: test
namespace: test
port: 8080There's nothing special about the deployment except that it initially starts out with zero replicas and has the sablier labels added apiVersion: apps/v1
kind: Deployment
metadata:
name: test
namespace: test
labels:
app: test
sablier.enable: "true"
sablier.group: "test"
spec:
replicas: 0As you can see we utilize the Traefik ...
providers:
kubernetesCRD:
allowCrossNamespace: true
allowEmptyServices: true
experimental:
plugins:
sablier:
moduleName: "github.com/acouvreur/sablier"
version: "v1.4.0-beta.3" |
|
This is the static configuration apiVersion: v1
kind: ConfigMap
metadata:
name: sablier-config
data:
sablier.yaml: |
provider:
# Provider to use to manage containers (docker, swarm, kubernetes)
name: kubernetes
server:
# The server port to use
port: 10000
# The base path for the API
base-path: /
storage:
# File path to save the state (default stateless)
file:
sessions:
# The default session duration (default 5m)
default-duration: 15m
# The expiration checking interval.
# Higher duration gives less stress on CPU.
# If you only use sessions of 1h, setting this to 5m is a good trade-off.
expiration-interval: 60s
logging:
level: debug
strategy:
dynamic:
# Custom themes folder, will load all .html files recursively (default empty)
custom-themes-path:
# Show instances details by default in waiting UI
show-details-by-default: true
# Default theme used for dynamic strategy (default "hacker-terminal")
default-theme: hacker-terminal
# Default refresh frequency in the HTML page for dynamic strategy
default-refresh-frequency: 10s
blocking:
# Default timeout used for blocking strategy (default 1m)
default-timeout: 5mThis is mounted under - name: sablier
image: acouvreur/sablier:1.3.0
args:
- "start"
- "--configFile=/sablier.yaml" |
- name: sablier
image: acouvreur/sablier:1.3.0
args:
- "start"
- "--configFile=/sablier.yaml" Here you are using version 1.3.0 which does not yet support groups, can you use the beta tag instead and try it out? |
|
Apologies copy-paste error. I tried both. I can confirm the problem exists with the |
|
Hello, I am seeing the same issue too using In case it's useful, this is the output of a If I change the service to use HTTP instead of HTTPs, I get the correct dynamic loading page and then I get the correct redirect. Given everything else works it feels like the issue could be around this call to sablier/plugins/traefik/main.go Line 43 in 98f0f81 |
|
🎉 This issue has been resolved in version 1.4.0-beta.7 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 1.4.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Describe the bug
When a group is scaling up and dynamic strategy is used, I expect to see the themed loading page. Instead I just see a pending request from the browser (so blank page).
Context
Expected behavior
When using the following middleware:
I would expect to see the loading page until pods are ready. However, the request does not complete and remains pending.
Additional context
port-forwardto thesablierpod, and I issue a request tohttp://localhost:10000/api/strategies/dynamic?group=testI do see the page.The text was updated successfully, but these errors were encountered: