CHANGELOG-1.0: update

Signed-off-by: Gyuho Lee <leegyuho@amazon.com>

Author: gyuho

CHANGELOG-1.0.md

@@ -9,7 +9,7 @@ See [code changes](https://github.com/aws/aws-k8s-tester/compare/v1.0.1...v1.0.2
 
 ### `eks-utils`
 
-- Add [`eks-utils`](https://github.com/aws/aws-k8s-tester/commit/).
+- Add [`eks-utils`](https://github.com/aws/aws-k8s-tester/commit/198631e1ae10ed4eb1a76346e27730290eb0675b).
   - Read https://github.com/aws/aws-k8s-tester#eks-utils.
 
 ### `aws-k8s-tester`
@@ -46,10 +46,6 @@ See [code changes](https://github.com/aws/aws-k8s-tester/compare/v1.0.1...v1.0.2
 - Add [`k8sclient.EKS.FetchServerVersion`](https://github.com/aws/aws-k8s-tester/commit/56cd2d0f26e88f8c806a74a503def91769a3e8e3).
 - Include [`float64` version value in `ServerVersionInfo`](https://github.com/aws/aws-k8s-tester/commit/).
 
-### Dependency
-
-- Upgrade [`github.com/aws/aws-sdk-go`](https://github.com/aws/aws-sdk-go/releases) from [`v1.30.7`](https://github.com/aws/aws-sdk-go/releases/tag/v1.30.7) to [`v1.30.X`](https://github.com/aws/aws-sdk-go/releases/tag/v1.30.X).
-
 ### Go
 
 - Compile with [*Go 1.14.2*](https://golang.org/doc/devel/release.html#go1.14).

README.md

@@ -199,11 +199,7 @@ less +FG /tmp/config.yaml
 
 Install `eks-utils` from https://github.com/aws/aws-k8s-tester/releases.
 
-**WARNING**
-
-`kubectl` internally converts API versions in the response (see [`kubernetes/issues#58131`](https://github.com/kubernetes/kubernetes/issues/58131#issuecomment-403829566)). Which means `kubectl get` output may have different API versions than the one persisted in `etcd`.
-
-Upstream recommends upgrading deprecated API with *get and put*:
+**WARNING**: `kubectl` internally converts API versions in the response (see [`kubernetes/issues#58131`](https://github.com/kubernetes/kubernetes/issues/58131#issuecomment-403829566)). Which means `kubectl get` output may have different API versions than the one persisted in `etcd` . Upstream Kubernetes recommends upgrading deprecated API with *get and put*:
 
 > the simplest approach is to get/put every object after upgrades. objects that don't need migration will no-op (they won't even increment resourceVersion in etcd). objects that do need migration will persist in the new preferred storage version