2017-08-03 86 views
0

因此,我正在zipkin中收集來自其他服務的kubernetes內的數據。我正在定義nginx入口控制器來公開我的服務,所有的作品都很好。由於zipkin是管理的事情,我很想把它放在一些安全性的後面。基本身份驗證。如果我加3線標記爲「#problematic行 - 開始」和「#problematic線 - 停止」下面我基普金前不再可見,我得到503kubernetes nginx ingress zipkin basic-auth

它與https://github.com/kubernetes/ingress/tree/master/examples/auth/basic/nginx ,沒有困難的事情在這裏產生。

apiVersion: v1 
kind: Service 
metadata: 
    name: zipkin 
    labels: 
    app: zipkin 
    tier: monitor 
spec: 
    ports: 
    - port: 9411 
    targetPort: 9411 
    selector: 
    app: zipkin 
    tier: monitor 
--- 
apiVersion: apps/v1beta1 
kind: Deployment 
metadata: 
    name: zipkin 
spec: 
    replicas: 1 
    template: 
    metadata: 
     labels: 
     app: zipkin 
     tier: monitor 
    spec: 
     containers: 
     - name: zipkin 
     image: openzipkin/zipkin 
     resources: 
      requests: 
      memory: "300Mi" 
      cpu: "100m" 
      limits: 
      memory: "500Mi" 
      cpu: "250m" 
     ports: 
     - containerPort: 9411 
--- 
apiVersion: v1 
kind: Service 
metadata: 
    name: zipkin-ui 
    labels: 
    app: zipkin-ui 
    tier: monitor 
spec: 
    ports: 
    - port: 80 
    targetPort: 80 
    selector: 
    app: zipkin-ui 
    tier: monitor 
--- 
apiVersion: apps/v1beta1 
kind: Deployment 
metadata: 
    name: zipkin-ui 
spec: 
    replicas: 1 
    template: 
    metadata: 
     labels: 
     app: zipkin-ui 
     tier: monitor 
    spec: 
     containers: 
     - name: zipkin-ui 
     image: openzipkin/zipkin-ui 
     resources: 
      requests: 
      memory: "300Mi" 
      cpu: "100m" 
      limits: 
      memory: "500Mi" 
      cpu: "250m" 
     ports: 
     - containerPort: 80 
     env: 
     - name: ZIPKIN_BASE_URL 
      value: "http://zipkin:9411" 
--- 
apiVersion: extensions/v1beta1 
kind: Ingress 
metadata: 
    name: zipkin 
    namespace: default 
    annotations: 
    kubernetes.io/ingress.class: "nginx" 
    ingress.kubernetes.io/enable-cors: "true" 
    ingress.kubernetes.io/ssl-redirect: "false" 
#problematic lines - start 
    ingress.kubernetes.io/auth-type: basic 
    ingress.kubernetes.io/auth-secret: basic-auth 
    ingress.kubernetes.io/auth-realm: "Authentication Required" 
#problematic lines - stop 
spec: 
    rules: 
    - host: "zipkin.lalala.com" 
    http: 
     paths: 
     - path:/
     backend: 
      serviceName: zipkin-ui 
      servicePort: 80 

我不知道,如果它不是可能infulence但我用https://github.com/kubernetes/ingress/blob/master/controllers/nginx/rootfs/etc/nginx/nginx.conf文件作爲模板,我的nginx的入口控制器我需要修改一些CORS規則。我看到部分:

{{ if $location.BasicDigestAuth.Secured }} 
{{ if eq $location.BasicDigestAuth.Type "basic" }} 
auth_basic "{{ $location.BasicDigestAuth.Realm }}"; 
auth_basic_user_file {{ $location.BasicDigestAuth.File }}; 
{{ else }} 
auth_digest "{{ $location.BasicDigestAuth.Realm }}"; 
auth_digest_user_file {{ $location.BasicDigestAuth.File }}; 
{{ end }} 
proxy_set_header Authorization ""; 
{{ end }} 

但我看不到結果:kubectl exec nginx-ingress-controller-lalala-lalala -n kube-system cat /etc/nginx/nginx.conf | grep auth。由於這個我的猜測是我需要添加一些註釋來使{{ if $location.BasicDigestAuth.Secured }}部分工作。不幸的是我找不到任何關於它的事情。

回答

0

我在我的入口9.0-beta.11上運行相同的配置。我想這只是一種錯誤配置。

首先,我會建議您不要更改模板並使用默認值,只需在basic-auth工作時更改。

入口日誌顯示給你什麼?您是否在入口資源的相同名稱空間中創建了basic-auth文件?

相關問題