-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
chore(eks): Remove legacy and deprecated code #12189
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.
So refreshing
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Do it!
…On Mon, Dec 21, 2020 at 6:29 PM Eli Polonsky ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In ***@***.***/aws-eks/lib/cluster.ts
<#12189 (comment)>:
> - * drop-in replacement for `eks.Cluster` with `kubectlEnabled: false`.
- *
- * Bear in mind that this is a temporary workaround. We have plans to remove
- * `eks.LegacyCluster`. If you have a use case for using `eks.LegacyCluster`,
- * please add a comment here #9332 and
- * let us know so we can make sure to continue to support your use case with
- * `eks.Cluster`. This issue also includes additional context into why this
- * class is being removed.
- *
- * @deprecated `eks.LegacyCluster` is __temporarily__ provided as a drop-in
- * replacement until you are able to migrate to `eks.Cluster`.
- *
- * @see #9332
- * @default true
- */
- readonly kubectlEnabled?: boolean;
I was having doubts about this since it might cause some minor breakage,
but thought it's probably ok since it was deprecated...
Any objections?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12189 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAIL5YBRTRRPPCXWMZ7YC3SV7K6DANCNFSM4VE3RP6Q>
.
--
Philip M. Gollucci
IT Executive and Engineering Leader
http://www.linkedin.com/in/pgollucci/
301.818.0719
|
Removing `LegacyCluster` and the `kubectlEnabled` property. Closes aws#11929 BREAKING CHANGE: `LegacyCluster` was removed since it existed only for a transition period to allow gradual migration to the current cluster class. - eks: `kubectlEnabled` property was removed, all clusters now support `kubectl`. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Removing
LegacyCluster
and thekubectlEnabled
property.Closes #11929
BREAKING CHANGE:
LegacyCluster
was removed since it existed only for a transition period to allow gradual migration to the current cluster class.kubectlEnabled
property was removed, all clusters now supportkubectl
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license