-
Notifications
You must be signed in to change notification settings - Fork 764
Update kube-proxy 1.33 version in documentation #1155
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
update nodeadm uninstall documentation
* Control Plane Logs Query for Karpenter Actions * fix hyperlink to karpenter gh * Update auto-troubleshoot.adoc * Update to include suggestions Co-authored-by: Chris Negus <striker57@gmail.com> * Update to include suggestions Co-authored-by: Chris Negus <striker57@gmail.com> * Update to include suggestions Co-authored-by: Chris Negus <striker57@gmail.com> * Update to include suggestions Co-authored-by: Chris Negus <striker57@gmail.com> --------- Co-authored-by: Chris Negus <striker57@gmail.com>
Adding more information on the Auto Mode’s logic when ephemeralStorage.size equals or exceeds the local NVMe capacity.
Add podSecurityGroupSelectorTerms to the schema for NodeClass for Auto Mode.
Add change notification and documentation for FIPS AMI support.
feat: document nodeclass FIPS support
Remove note about IAM role usage for Windows nodes
Clarified Amazon EKS Auto Mode support for Fault Injection Service actions and added details on supported and unsupported actions.
Update EKS-optimized GPU AMI docs
Update security-groups-for-pods.adoc
Fixed link syntax and minor style rewrites
…dates Update EKS Auto Fault Injection Service support details
Additional Information on CoreDNS in EKS Auto Mode
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Contributor
|
I apologize, due to a required migration this PR had to be closed. We will review the closed PRs and make appropriate updates. You are welcome to re-submit your changes. We appreciate every contribution and apologize for the inconvenience. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Changes kube-proxy 1.33 version in documentation to
eksbuild.10aseksbuild.11does not exist.Running:
Outputs:
Clearly, the last version is
eksbuild.10and noteksbuild.11. Having this fixed will save some debugging time to users.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.