Add limitiations doc for manageTLS #562
Conversation
Document that runtime components are responsible for making use of the TLS certificates created by the operator when mangeTLS=true
idlewis
force-pushed
the
538-doc-update
branch
from
d7296d3
to
734be06
Compare
doc/user-guide-v1.adoc
Outdated
|
|
||
| == Limitations | ||
| === Using certificates when manageTLS=true | ||
| If `manageTLS=true` is specified in the CR YAML file, then the operator will manage the creation of a TLS secret for the runtime component. |
There was a problem hiding this comment.
manageTLS is true by default - even if it's not specified in CR YAML. It'll be good to mention/clarify so that users don't remove it and expect manageTLS to be false
@leochr I'm not quite sure how to use the comment from Tam. There seem to be two suggestions on how to work around this issue with tWAS, but I'm guessing that the correct solution would depend on the tWAS configuration. Were you thinking of documenting a specific use case, such as: |
|
@idlewis Specific use cases would be more helpful. The troubleshooting doc would be more appropriate than the Limitations section I guess to hold such information. Thanks |
As this version of the operator is no longer supported
|
tagging myself as a reminder to review @leochr |
Document that runtime components are responsible for making use of the TLS certificates created by the operator when mangeTLS=true
deals with issue #538