-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Reword the changelog fragments to better generate the CHANGELOG.md when we release 1.0. #3544
Conversation
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 am ok with the fixes in the changelog. 👍
/lgtm
However, as we spoke I think we can simplify by combining some changes. Add here my suggestions as well.
Ansible & Helm-based Operators switched to using the `InstrumentedEnqueueRequestForObject` from | ||
[operator-lib](https://github.com/operator-framework/operator-lib/blob/main/handler/instrumented_enqueue_object.go) | ||
instead of controller-runtime's `EnqueueRequestForObject`. |
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.
This should be consolidated with the removal of legacy metrics generation in Helm and Ansible operators fragments (again, in the release prep PR)
@@ -2,7 +2,7 @@ | |||
# release notes and/or the migration guide | |||
entries: | |||
- description: > | |||
The commands `operator-sdk new --type=ansible` and `operator-sdk add api` are no longer supported for Ansible-based Operators. | |||
Removed legacy `new` and `add api` commands from Ansible-based Operators. |
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.
All legacy removals IMO could be replaced for one fragment:
# entries is a list of entries to include in
# release notes and/or the migration guide
entries:
- description: >
Remove support for the legacy layout. Operator SDK has a new CLI and project layout that is aligned with Kubebuilder. (//todo: add all pr's numbers)
kind: "removal"
# Is this a breaking change?
breaking: yes
# Migration can be defined to automatically add a section to
# the migration guide. This is required for breaking changes.
migration:
header: Migrate your projects for the new layout
body: >
Operator SDK has a new CLI and project layout that is aligned with Kubebuilder.
See `operator-sdk init -h` and the following doc on how to scaffold a new project:
To migrate existing projects to the new layout see the migrations guides in
https://sdk.operatorframework.io.
- For Go-based Operators: https://master.sdk.operatorframework.io/docs/building-operators/golang/project_migration_guide/
- For Helm-based Operators: https://master.sdk.operatorframework.io/docs/building-operators/helm/migration/
- For Ansible-based Operators: TBD
Wdyt @joelanford
Added `--metrics-addr` flag to helm operator to make it configurable, and | ||
changed the default from `:8383` to `:8080` | ||
Added `--metrics-addr` flag to the Helm operator to make it configurable, and | ||
changed the default port from `:8383` to `:8080` |
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.
IMO we can combine the metrics change for Ansible and Helm:
Breaking change: (Valid only for Ansible/Helm-based Operators). Added --metrics-addr flag to make it configurable, and changed the default port used by the metric endpoint binds to from :8383 to :8080. (#3489, #3440)
61adfa1
to
ef724c0
Compare
New changes are detected. LGTM label has been removed. |
ef724c0
to
70d30a4
Compare
3dd4888
to
263e232
Compare
Closing this pull request in favor of the upcoming release PR. |
Description of the change:
Reword the changelog fragments to better generate the CHANGELOG.md when we release 1.0.
Motivation for the change:
Preparing for a 1.0 CHANGELOG.
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments
(seechangelog/fragments/00-template.yaml
)website/content/en/docs