-
-
Notifications
You must be signed in to change notification settings - Fork 410
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
Example of K8s conf #33
Comments
I will add this into the example shortly, thanks |
sorry that i am a newbie. How can i access the traefik-dashboard with this example? Do i need to add another service to serve this? |
I don't think so, to expose the dashboard, you need to make sure you are exposing the port from the traefik container: ports:
- name: http
containerPort: 80
hostPort: 80
protocol: TCP
- name: https
containerPort: 443
hostPort: 443
protocol: TCP
- name: dash
containerPort: 8080
protocol: TCP Any then by creating a service and ingress: ---
#
# Dash Service
#
apiVersion: v1
kind: Service
metadata:
name: traefik-dashboard
labels:
app: traefik
spec:
type: ClusterIP
selector:
app: traefik
ports:
- name: dashboard-http
port: 8080
targetPort: 8080
---
#
# Dash Ingress
#
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: traefik-dashboard
labels:
app: traefik
spec:
rules:
- host: traefik.ourdomain.com
http:
paths:
- backend:
serviceName: traefik-dashboard
servicePort: dashboard-http |
I'm working on making an example helm chart to simplify the deployment a little. It's my first one however, and I'm having a little trouble. Can anyone point out what I'm doing wrong. Here are my computed service, deployment and secret:
and here is the error I'm getting:
|
Sorry I was able to figure out I had bad formatting for DEFAULT_PROVIDER, PROVIDERS_OIDC_ISSUER_URL, and the value for INSECURE_COOKIE. |
When I login with my organization account, I get this error: Not sure what is this. I am using with the following values.yaml:
|
Hi,
If you're interested, here is an example Kubernetes configuration for traefik-forward-auth using
AUTH_HOST
:And without the
AUTH_HOST
:And here is how to configure an authenticated ingress using annotations (equivalent to Compose / Swarm labels):
Also, here the command to encode the secrets in base64:
Best
The text was updated successfully, but these errors were encountered: