-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Clean up deprecated+removed cmd line flags #7294
Conversation
@@ -57,8 +57,6 @@ coreos: | |||
--cluster-dns=10.100.0.10 \ | |||
--cluster-domain=cluster.local \ | |||
--hostname-override=$private_ipv4 \ | |||
--logtostderr=true \ | |||
--network-plugin=cni \ |
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.
Was the removal of --network-plugin=cni
here intentional? Has it also been deprecated?
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 it was intentional, because of this commit: 25a6144 (though I admit I didn't research on which versions exactly this one was deprecated/removed)
…elease-v3.25 [release-v3.25] Auto pick #7294: Clean up deprecated+removed cmd line flags
…elease-v3.24 [release-v3.24] Auto pick #7294: Clean up deprecated+removed cmd line flags
Remove usage of deprecated '--logtostderr' command line flag in PrepareNode.ps1 scripts (projectcalico/calico#7294 for more details).
Remove usage of deprecated '--logtostderr' command line flag in PrepareNode.ps1 scripts (projectcalico/calico#7294 for more details).
Description
https://kubernetes.io/docs/concepts/cluster-administration/system-logs/ says these flags were deprecated in v1.23, and seem to have been removed in v1.26, and it also says "Output will always be written to stderr, regardless of the output format."
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*
label.docs-pr-required
: This change requires a change to the documentation that has not been completed yet.docs-completed
: This change has all necessary documentation completed.docs-not-required
: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*
label.release-note-required
: This PR has user-facing changes. Most PRs should have this label.release-note-not-required
: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate
: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr
: This PR is related to install and requires a corresponding change to the operator.