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

[SRVKS-1262] ContainerHealthy reset #838

Merged

Conversation

skonto
Copy link

@skonto skonto commented Sep 9, 2024

What this PR does / why we need it:

  • Temporary fix suggested upstream.
  • See related jira for the details.

@openshift-ci openshift-ci bot added the approved label Sep 9, 2024
@skonto skonto requested review from maschmid and removed request for alanfx and ReToCode September 9, 2024 10:38
@dsimansk
Copy link

dsimansk commented Sep 9, 2024

/approve
/lgtm

Copy link

openshift-ci bot commented Sep 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, skonto

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 4a9d614 into openshift-knative:release-v1.14 Sep 9, 2024
7 checks passed
@@ -117,6 +117,9 @@ func (c *Reconciler) reconcileDeployment(ctx context.Context, rev *v1.Revision)
}
}

if *deployment.Spec.Replicas > 0 && *deployment.Spec.Replicas == deployment.Status.ReadyReplicas {

Choose a reason for hiding this comment

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

Should it be compared to AvailableReplicas instead?

Copy link
Author

@skonto skonto Oct 24, 2024

Choose a reason for hiding this comment

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

@maschmid I had the same question. Afaik ready means available as we the deployment we create has the following set to 0:

	// Minimum number of seconds for which a newly created pod should be ready
	// without any of its container crashing, for it to be considered available.
	// Defaults to 0 (pod will be considered available as soon as it is ready)
	// +optional
	MinReadySeconds int32 `json:"minReadySeconds,omitempty" protobuf:"varint,5,opt,name=minReadySeconds"`

@maschmid
Copy link

/cherry-pick release-v1.15

@openshift-cherrypick-robot

@maschmid: new pull request created: #935

In response to this:

/cherry-pick release-v1.15

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 kubernetes-sigs/prow repository.

@maschmid
Copy link

/cherry-pick release-v1.16

@openshift-cherrypick-robot

@maschmid: new pull request created: #936

In response to this:

/cherry-pick release-v1.16

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 kubernetes-sigs/prow repository.

@skonto
Copy link
Author

skonto commented Oct 29, 2024

/cherry-pick release-v1.16

@openshift-cherrypick-robot

@skonto: new pull request created: #944

In response to this:

/cherry-pick release-v1.16

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 kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants