-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Rename eventing release artifacts release.yaml => eventing.yaml #2103
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
Rename eventing release artifacts release.yaml => eventing.yaml #2103
Conversation
| - https://github.com/knative/serving/releases/download/{{< version >}}/monitoring-tracing-zipkin.yaml | ||
| - https://github.com/knative/serving/releases/download/{{< version >}}/monitoring-tracing-zipkin-in-mem.yaml | ||
| - **Eventing Component**: | ||
| - https://github.com/knative/eventing/releases/download/{{< version >}}/release.yaml |
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.
Just to make sure I understand, @yolocs -- going forward, the only artifact released for eventing will be eventing.yaml, and it will come bundled with the in-memory channel provisioner? No more option to install it separately?
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.
Yes, that's my understanding. @grantr
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.
Cool, just wanted to make sure I understood what was changing :) I'll wait to merge this until the Eventing PR is merged.
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.
FYI. The eventing PR has been merged.
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.
the only artifact released for eventing will be eventing.yaml, and it will come bundled with the in-memory channel provisioner? No more option to install it separately?
No, this is incorrect. There will still be 3 artifacts:
eventing-core.yamlwill be just the eventing core without InMemoryChannel, equivalent to the previouseventing.yaml
in-memory-channel.yamlwill be just the InMemoryChannel, unchangedeventing.yamlwill be eventing-core.yaml and in-memory-channel.yaml combined, equivalent to the previousrelease.yaml
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.
If I understand it correctly, only eventing.yaml will actually be useful, right? I don't see serving list serving-core.yaml 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.
You're right, serving-core.yaml isn't documented here so eventing-core.yaml can also be undocumented. I was just answering @samodell's question about installing separately. That option will still exist, even if undocumented.
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 for clarifying.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: samodell, yolocs 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 |
Fixes knative/eventing#1987
Eventing PR: knative/eventing#2382
Proposed Changes