Update managing-kube-proxy.adoc #1170
Open
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
Added consideration for pod subnets
* add docs for the new associatePublicIPAddress field * add change log --------- Co-authored-by: Geoffrey Cline <geoffreyc@outlook.com>
…s#1082) * fix: fixed incorrect command for "Step 6: Scale down CoreDNS" * fix: fixed spelling issue
The aws eks create-cluster command was incorrect. The value in --resources-vpc-config subnetIds= argument had incorrect double quotations.
* hybrid node doc remove redundant newline * hybrid node doc add missing space * hybrid node doc fix broken link
Additional Information on CoreDNS in EKS Auto Mode
Highlight the generated key for NodeDiagnostic should be ends with .tar.gz
…er-access-policy Add AmazonEKSSecretReaderPolicy reference documentation in EKS Access Policy Reference
…ture document the new helm EBS CSI feaure for disabling mutating permissions
Update Cilium v1.17.9 and v1.18.3 support for EKS Hybrid Nodes
[AL2 EOS Prep] Update worker.adoc: AL2023/Nodeadm updates
[AL2 EOS Prep] Update cni-custom-network-tutorial.adoc
[AL2 EOS Prep] Update launch-templates.adoc
[AL2 EOS Prep] Update private-clusters.adoc to be specific to AL2023
…les (awsdocs#1167) This script analyzes all .adoc files in latest/ug/ to find broken xrefs. It processes files in parallel and detects both xref: and <<>> syntax forms, as well as multiple section ID formats including [[id]], [#id], and auto-generated IDs from section headers. The script reports: - Broken cross-references with file paths and line numbers - Duplicate section IDs across files - Summary statistics Results: Analyzed 394 files, found 3,878 section IDs and 2,241 xrefs, with only 2 broken xrefs (both placeholder examples in contribution docs). Co-authored-by: Claude <noreply@anthropic.com>
Update kube-proxy version to recommended in AWS console
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
Update kube-proxy version to latest in AWS console
Issue
Description of changes:
Update latest viable version in the documentation, as it was puking out the above mentioned error (checked Control Plane version 1.33 & 1.34)
v1.33
Attempted Upgrade (this failed)
Listed Versions in AWS
v1.34
Listed Versions in AWS
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.