-
Notifications
You must be signed in to change notification settings - Fork 225
Conversation
/assign @vaikas-google |
// +patchMergeKey=type | ||
// +patchStrategy=merge | ||
Conditions duckv1alpha1.Conditions `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type"` | ||
duckv1alpha1.Status `json:",inline"` |
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.
See knative/eventing#913 (comment). This needs documentation about what fields are embedded here.
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 don't think this comment will stay up to date for long. I am pushing back.
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.
That gives me pause.
This embed is published API that users and integrators see and work with and build knowledge and products around. If we rename ObservedGeneration
to SeenGeneration
, that's a breaking API change, and it should be documented.
If duckv1alpha1.Status
is going to be a shared interface, it can't change very often, and when it does, that change should be announced in every project that uses it.
/assign grantr |
/hold wait for #258 |
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.
Thanks @n3wscott!
/lgtm
Can you add something like this to the PR release note?
Upgrade to Kubernetes 1.12.6.
Added ObservedGeneration to all Source CRDs.
|
||
[[override]] | ||
name = "k8s.io/api" | ||
version = "kubernetes-1.12.5" | ||
version = "kubernetes-1.12.6" |
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'd probably mention this in release notes for completeness, but I don't think it's required.
Conditions duckv1alpha1.Conditions `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type"` | ||
// inherits duck/v1alpha1 Status, which currently provides: | ||
// * ObservedGeneration - the 'Generation' of the Service that was last processed by the controller. | ||
// * Conditions - the latest available observations of a resource's current state. |
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.
✨
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: grantr, n3wscott 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 |
/hold cancel pkg docs updated. |
Looks like you need to rerun codegen, which is odd because you just did that |
/lgtm |
Following knative/serving#3444
This embeds duckv1alpha1.Status (knative/pkg#324) in
all of our resource's status in place of having each independently define
ObservedGeneration and Conditions. The point of doing this is that Conditions
alone are insufficient to truly assess readiness because we also must make sure
that the generation that those conditions reflect (the observed generation)
matches the current generation of the resource (the metadata generation).
Also had to update the e2e test from pkg changes.
Release Note
combines #257