Fix syntax error in CRI-O drop-in file on Switching to EventedPLEG page#55696
Fix syntax error in CRI-O drop-in file on Switching to EventedPLEG page#55696namanraofullstack wants to merge 2 commits intokubernetes:mainfrom
Conversation
|
Welcome @namanraofullstack! |
feb998e to
b6d60d3
Compare
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @namanraofullstack, please only update the english version, and leave the other language for different localization teams. /hold |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
4dbbef0 to
91019f0
Compare
I have reverted the zh-cn changes and only updated the english version. |
|
Thanks, please squash your commits into a single one. /unhold |
|
/remove-language zh |
Description
Fixes a syntax error in the CRI-O drop-in configuration example for enabling the EventedPLEG feature.
The current documentation suggests the following configuration:
However, this results in a CRI-O configuration parsing error:
CRI-O configuration uses TOML syntax, where key-value assignments must use
=instead of:.This PR updates the example to:
This ensures the configuration is valid and prevents runtime errors when users attempt to enable EventedPLEG.
This change applies to both English and zh-cn translations.
Issue
Closes: #55670