docs: DOC-1385 #4047
docs: DOC-1385 #4047
Conversation
karl-cardenas-coding
added
auto-backport
karl-cardenas-coding
requested review from
addetz,
lennessyy and
caroldelwing
✅ Deploy Preview for docs-spectrocloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Co-authored-by: Lenny Chen <[email protected]>
* docs: 9-23-24 cve updates (#4046) * 9-23-24 cve updates * ci: auto-formatting prettier issues --------- Co-authored-by: frederickjoi <[email protected]> * docs: PEM-5725 * docs: review feedback * docs: vale feedback * docs: apply suggestions from code review Co-authored-by: caroldelwing <[email protected]> * ci: auto-formatting prettier issues * docs: feedback updates --------- Co-authored-by: frederickjoi <[email protected]> Co-authored-by: frederickjoi <[email protected]> Co-authored-by: caroldelwing <[email protected]> Co-authored-by: karl-cardenas-coding <[email protected]>
| @@ -43,3 +43,4 @@ Ongoing | |||
|
|
|||
| - 1.0 08/16/2024 Initial Publication | |||
| - 2.0 08/17/2024 Added palette VerteX 4.4.14 to Affected Products | |||
| - 3.0 9/23/2024 Changed CVE status to Resolved | |||
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '9/23/2024'.
| @@ -41,3 +41,4 @@ Ongoing | |||
|
|
|||
| - 1.0 08/16/2024 Initial Publication | |||
| - 2.0 08/17/2024 Added Palette VerteX 4.4.14 to Affected Products | |||
| - 3.0 09/23/2024 Changed CVE status to Resolved | |||
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '09/23/2024'.
| @@ -41,3 +41,4 @@ Ongoing | |||
|
|
|||
| - 1.0 07/16/2024 Initial Publication | |||
| - 2.0 08/17/2024 Remediated in Palette VerteX 4.4.14 | |||
| - 3.0 09/23/2024 Changed CVE status to Resolved | |||
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '09/23/2024'.
| @@ -41,3 +41,4 @@ Ongoing | |||
|
|
|||
| - 1.0 08/16/2024 Initial Publication | |||
| - 2.0 08/17/2024 Added palette VerteX 4.4.14 to Affected Products | |||
| - 3.0 09/23/2024 Changed CVE status to Resolved | |||
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '09/23/2024'.
| @@ -44,3 +44,4 @@ Ongoing | |||
|
|
|||
| - 1.0 08/16/2024 Initial Publication | |||
| - 2.0 08/17/2024 Added palette VerteX 4.4.14 to Affected Products | |||
| - 3.0 09/23/2024 Changed CVE status to Resolved | |||
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '09/23/2024'.
| service. | ||
| 2. The agent's in-memory proxy creates a WebSocket connection with the management plane servers. | ||
| 3. The management plane server accepts the WebSocket connection | ||
| 4. The agent in-memory proxy transcodes the gRPC request on-demand and sends it via the WebSocket connection. |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'transcodes'?
| handler. | ||
| 6. The gRPC handler processes the request and responds via the same connection. The WebSocket handler sends the response | ||
| from the gRPC handler back to the agent. | ||
| 7. The agent's in-memory proxy reads the response off the WebSocket connection and transcodes it back to HTTP/2 and |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'transcodes'?
| 7. The agent's in-memory proxy reads the response off the WebSocket connection and transcodes it back to HTTP/2 and | ||
| passes it to the agent. | ||
|
|
||
| A more straightforward way to think about the WebSocket transcoding architecture is that network traffic between the |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'transcoding'?
|
|
||
| A more straightforward way to think about the WebSocket transcoding architecture is that network traffic between the | ||
| Palette agent and the management plane uses the WebSocket connection and the HTTP/1.1 protocol. The agent and server are | ||
| still communicating using gRPC, but the messages are transcoded to the HTTP/1.1 protocol between the two entities. Using |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'transcoded'?
| The following sections provide information about using gRPC with network proxies. These issues are addressed by using | ||
| WebSocket and the HTTP/1.1 protocol as a fallback mechanism. However, if you want to better understand the reasons for | ||
| falling back to a WebSocket connection, the following sections provide more information about challenges with gRPC and | ||
| network proxies. If you want to learn more about gRPC and transcoding, check out the Red Hat article |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'transcoding'?
| over WebSocket. Palette agents will automatically fall back to a WebSocket connection if the gRPC connection cannot be | ||
| established with the management plane using the default HTTP/2 protocol. This change improves the reliability of the | ||
| communication channel between the agent and the management plane. Environments with network proxies that reject HTTP/2 | ||
| connections can now connect as the connection is transcoded to the HTTP/1.1 protocol. Refer to the |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'transcoded'?
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
|
🎉 This issue has been resolved in version 4.5.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Describe the Change
This PR adds release notes for an upcoming patch.
Changed Pages
💻 Preview URL for Page
Jira Tickets
🎫 DOC-1385
Backports
Can this PR be backported?