Skip to content
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

operator: add explicit non blocking handling of Pod deletion #122

Merged
merged 1 commit into from
Apr 6, 2021

Conversation

kkujawa-sumo
Copy link
Contributor

Trying to change volumeMount type from string to
VolumeMount from k8s.io/api/core/v1 observed that
when Pod is modified through kubectl apply --force deletion hangs

Related to #55 and #119

@kkujawa-sumo kkujawa-sumo requested a review from a team as a code owner April 2, 2021 08:49
Copy link
Contributor

@andrzej-stencel andrzej-stencel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤯 this is weird!

@@ -62,6 +63,10 @@ type PodExtender struct {

// Handle handles requests to create/update Pod and extends it by adding tailing sidecars
func (e *PodExtender) Handle(ctx context.Context, req admission.Request) admission.Response {
if req.Operation == admv1.Delete {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a more descriptive comment about the situation when this happens and what this if is trying to solve

Trying to change volumeMount type from string to
VolumeMount from k8s.io/api/core/v1 observed that
when Pod is modified through kubectl apply --force deletion hangs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants