[GitHub] [pulsar-helm-chart] vitosans commented on issue #84: TLS Authentication in Kubernetes, Pulsar 2.6.1 - Broker crash loop on startup due to 401 in WorkerService.start(..)

[GitBox]

vitosans commented on issue #84:
URL: 
https://github.com/apache/pulsar-helm-chart/issues/84#issuecomment-932431670


   I did something like this: 
   
   tlsEnabled: "true"
   brokerClientTlsEnabled: "true"
   brokerClientTrustCertsFilePath: "/pulsar/certs/ca/ca.crt"
   useTls: true
   tlsCertificateFilePath: "/pulsar/certs/broker/tls.crt"
   tlsKeyFilePath: "/pulsar/certs/broker/tls.key"
   tlsTrustCertsFilePath: "/pulsar/certs/ca/ca.crt"
   tlsAllowInsecureConnection: false
   tlsEnableHostnameVerification: false
   tlsCertRefreshCheckDurationSec: 300
   
   In broker-configmap.yaml
   
   The broker is now able to start up when functions are enabled. Now the 
problem is when you deploy a function the functions_worker that gets spawned 
off has a default functions_works.yaml and not the one generated from 
bin/gen-yml-from-env.py conf/functions_worker.yml in the StateFullSet
   
   So of course he now gets a:
   
   HTTP 401 Unauthorized                                                        
                                                                                
             │
   Reason: HTTP 401 Unauthorized
   
   as he is trying to post to http://localhost:8080 which of course is wrong :) 
   
   Trying to debug this currently, and then make a giant PR that enables mTLS 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org