mirror of https://github.com/k3s-io/k3s
Merge pull request #37478 from YuPengZTE/devMD037
Automatic merge from submit-queue fix the mistake type <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note ``` Signed-off-by: yupeng <yu.peng36@zte.com.cn>pull/6/head
commit
7a57e80ef6
|
@ -198,7 +198,7 @@ Within the AWS cloud provider logic, we filter requests to the AWS APIs to
|
|||
match resources with our cluster tag. By filtering the requests, we ensure
|
||||
that we see only our own AWS objects.
|
||||
|
||||
** Important: ** If you choose not to use kube-up, you must pick a unique
|
||||
**Important:** If you choose not to use kube-up, you must pick a unique
|
||||
cluster-id value, and ensure that all AWS resources have a tag with
|
||||
`Name=KubernetesCluster,Value=<clusterid>`.
|
||||
|
||||
|
|
Loading…
Reference in New Issue