TRACING-5321: RHOSDT 3.6 OTEL document TPM #93211
Conversation
Signed-off-by: Pavol Loffay <p.loffay@gmail.com>
openshift-ci-robot
added
the
jira/valid-reference
|
@pavolloffay: This pull request references TRACING-5321 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Skipping CI for Draft Pull Request. |
openshift-ci
bot
added
do-not-merge/work-in-progress
| <5> Specifies the time interval at which the certificate is reloaded. If the value is not set, the certificate is never reloaded. The `reload_interval` accepts a string containing valid units of time such as `ns`, `us` (or `µs`), `ms`, `s`, `m`, `h`. | ||
| <6> Overrides the virtual host name of authority such as the authority header field in requests. You can use this for testing. | ||
| <7> Headers are sent for every request performed during an established connection. | ||
| <7> Enables reading the TSS2 private key (`key_file`) from Trusted Platform Module (TPM). The default value is `false`. |
There was a problem hiding this comment.
@max-cx can we add Tech preview to point 7 and 8 ?
|
Closing the feature will not be documented as of now |
2 participants
Version(s):
OCP 4.12-4.19
RHOSDT 3.6
Issue:
https://issues.redhat.com/browse/TRACING-5321
Link to docs preview:
QE review:
Additional information: