-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KEP-4396 Fix beta stage description #4926
Conversation
HirazawaUi
commented
Oct 20, 2024
- One-line PR description: Fixed incorrect description when promoting to beta stage
- Issue link: Allow almost all printable ASCII characters in environment variables #4369
- Other comments:
- [x] Metrics | ||
- Metric name: run_podsandbox_errors_total | ||
- [ ] Metrics | ||
- Metric name: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed this metric because we didn't affect the RunPodSandbox
call; we only impacted the CreateContainer
phase, which was an earlier mistake of mine. Or do we need to add a new metric at the CreateContainer
phase, such as create_container_error
? I'm not sure if we really need it. Please refer to the URL of the test project pointed out in the KEP. So far, I haven't found any scenarios where relaxed environment variable names cause container runtime errors.
Since the freeze for enhancements has passed, I am not sure if this PR will still be accepted. Should we merge this PR? |
@@ -224,7 +224,9 @@ Yes. | |||
|
|||
### Rollout, Upgrade and Rollback Planning | |||
|
|||
When the feature gate is disabled, workloads that are already running will not be affected. If environment variables contain special characters, changes to fields other than the environment variables will not cause workloads to fail. However, if the environment variable fields are modified, they may fail to recreate Pods or ReplicaSets due to the Apiserver's validation logic, which could result in workload failures. | |||
###### How can a rollout or rollback fail? Can it impact already running workloads? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reverted it to the previous description of #4805 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add the job you added for this?
ec37ec7
to
8bd70a9
Compare
Added. |
/lgtm |
/unassign @dchen1107 @mrunalp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: HirazawaUi, SergeyKanzhelev The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |