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

Only set Latest to LatestCreated revision #173

Merged
merged 3 commits into from
Feb 14, 2018

Conversation

yanweiguo
Copy link
Contributor

If the ready revision is not the latest created one, we should not set it to Configuration.Status.Latest. Fixes #77.

@@ -437,7 +441,10 @@ func (c *Controller) markConfigurationReady(
Status: corev1.ConditionTrue,
Reason: "LatestRevisionReady",
})

glog.Infof("Seting Latest of Configuration %q to revision %q", config.Name, revision.Name)
config.Status.Latest = revision.Name
Copy link
Member

Choose a reason for hiding this comment

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

Can we rename Latest to LatestReady. I think this was a misnomer that we corrected in the API draft that was never reflected here.

Copy link
Member

@mattmoor mattmoor left a comment

Choose a reason for hiding this comment

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

I wonder about starvation in fast-moving repositories, but I think this is probably fine.

@yanweiguo yanweiguo merged commit cfe0789 into knative:master Feb 14, 2018
@yanweiguo yanweiguo deleted the mark_latest_only_become_ready branch February 14, 2018 21:19
lberk pushed a commit to lberk/serving that referenced this pull request Jul 4, 2019
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

2 participants