steveniemitz commented on PR #21457:
URL: https://github.com/apache/flink/pull/21457#issuecomment-1339512174

   > In the operator there is already such solution: 
https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/ssl/ReloadableSslContext.java
   > 
   > Who will track the cert changes this case? An SSLContext can't reload 
itself.
   
   I think that's a good example of what this could be used for.  You could, 
for example, return that ReloadingSslContext from a supplier configured with 
this.  
   
   The implementer of the supplier can chose to track the changes however they 
want, so it'd be up to the implementation to determine when to reload the 
context.


-- 
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: issues-unsubscr...@flink.apache.org

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

Reply via email to