Minor update to documentation for deploy, overview, and readme.md pages (#506)

* Add linter config

* Doc: Update deployment doc prefix lists

Add IPv4 and IPv6 prefix list Ids to security group ingress onboarding step instead of the specific IP range used by the Lattice network.

* Doc: Update development doc with prefix lists

Add IPv4 and IPv6 prefix list Ids to security group ingress onboarding step instead of the specific IP range used by the Lattice network.

* ci: Use mattn/goveralls instead of shogo821/goveralls

* ci: Use mattn/goveralls instead of shogo821/goveralls

* doc: update overview page for v1

* Doc: Update readme

* doc: add link to SG docs in deploy

* nit: space and wording cleanup

Author: graehren

README.md

@@ -1,16 +1,62 @@
 # AWS Gateway API Controller for VPC Lattice
 
 <p align="center">
-    <img src="docs/images/kubernetes_icon.svg" alt="Kubernetes logo" width="200" />
-    <img src="docs/images/controller.png" alt="AWS Load Balancer logo" width="200" />
+    <img src="docs/images/kubernetes_icon.svg" alt="Kubernetes logo" width="100" /> 
+    <img src="docs/images/controller.png" alt="AWS Load Balancer logo" width="100" />
 </p>
 
 AWS Application Networking is an implementation of the Kubernetes [Gateway API](https://gateway-api.sigs.k8s.io/). This project is designed to run in a Kubernetes cluster and orchestrates AWS VPC Lattice resources using Kubernetes Custom Resource Definitions like Gateway and HTTPRoute.
 
+## Documentation
+
+### Website
+
+The API specification and detailed documentation is available on the project
+website: [https://www.gateway-api-controller.eks.aws.dev/][ghp].
+
+### Concepts
+
+To get started, please read through [API concepts][concepts] and
+[Security model][security-model]. These documents give the necessary background
+to understand the API and the use-cases it targets.
+
+### Getting started
+
+Once you have a good understanding of the API at a higher-level, check out
+[getting started][getting-started] to install your first Gateway controller and try out
+one of the guides.
+
+### References
+
+A complete API reference, please refer to:
+
+- [API reference][spec]
+- [Go docs for the package][godoc]
+
+## Contributing
+
+Developer guide can be found on the [developer guide page][dev].
+Our Kubernetes Slack channel is [#aws-gateway-api-controller][slack].
+
+### Code of conduct
+
+Participation in the Kubernetes community is governed by the
+[Kubernetes Code of Conduct](code-of-conduct.md).
+
 ## Security
 
 See [CONTRIBUTING](CONTRIBUTING.md#security-issue-notifications) for more information.
 
 ## License
 
 This project is licensed under the Apache-2.0 License.
+
+[ghp]: https://www.gateway-api-controller.eks.aws.dev/
+[dev]: https://www.gateway-api-controller.eks.aws.dev/developer/
+[slack]: https://kubernetes.slack.com/messages/aws-gateway-api-controller
+[getting-started]: https://www.gateway-api-controller.eks.aws.dev/getstarted/
+[spec]: https://www.gateway-api-controller.eks.aws.dev/reference/grpc-route/
+[concepts]: https://www.gateway-api-controller.eks.aws.dev/configure/
+[security-model]: https://gateway-api.sigs.k8s.io/concepts/security-model
+[gh_release]: https://github.com/aws/aws-application-networking-k8s/releases/tag/v0.0.18
+[godoc]: https://www.gateway-api-controller.eks.aws.dev/

docs/deploy.md

@@ -10,11 +10,12 @@ Run through them again for a second cluster to use with the extended example sho
    export AWS_REGION=us-west-2
    export CLUSTER_NAME=my-cluster
    ```
-1. You can use an existing EKS cluster or create a new one as shown here:
+2. You can use an existing EKS cluster or create a new one as shown here:
    ```bash
    eksctl create cluster --name $CLUSTER_NAME --region $AWS_REGION
    ```
-2. First, configure security group to receive traffic from the VPC Lattice network. You must set up security groups so that they allow all Pods communicating with VPC Lattice to allow traffic from the VPC Lattice managed prefix lists. Lattice has both an IPv4 and IPv6 prefix lists available.
+3. Configure security group to receive traffic from the VPC Lattice network. You must set up security groups so that they allow all Pods communicating with VPC Lattice to allow traffic from the VPC Lattice managed prefix lists.  See [Control traffic to resources using security groups](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html) for details. Lattice has both an IPv4 and IPv6 prefix lists available.
+
     ```bash
     CLUSTER_SG=$(aws eks describe-cluster --name $CLUSTER_NAME --output json| jq -r '.cluster.resourcesVpcConfig.clusterSecurityGroupId')
     PREFIX_LIST_ID=$(aws ec2 describe-managed-prefix-lists --query "PrefixLists[?PrefixListName=="\'com.amazonaws.$AWS_REGION.vpc-lattice\'"].PrefixListId" | jq -r '.[]')

docs/images/fundamentals-mapping-25dce4c9307fc185a4143b37c759d154.png

@@ -1,10 +1,16 @@
 # AWS Gateway API Controller User Guide
 
-The AWS Gateway API Controller lets you connect services across multiple Kubernetes clusters through the Kubernetes Gateway API interface.
-It is also designed to connect services running on EC2 instances, containers, and as serverless functions.
-It does this by leveraging Amazon VPC Lattice, which works with Kubernetes Gateway API calls to manage Kubernetes objects. 
+The AWS Gateway API controller integrates VPC Lattice with the Kubernetes Gateway API. When installed in your cluster, the controller watches for the creation of Gateway API resources such as gateways and routes and provisions corresponding Amazon VPC Lattice objects. This enables users to configure VPC Lattice Service Networks using Kubernetes APIs, without needing to write custom code or manage sidecar proxies. The AWS Gateway API Controller is an open-source project and fully supported by Amazon.
+
+AWS Gateway API Controller integrates with Amazon VPC Lattice and allows you to:
+
+* Handle network connectivity seamlessly between services across VPCs and accounts.
+* Discover these services spanning multiple Kubernetes clusters
+* Implement a defense-in-depth strategy to secure communication between those services.
+* Observe the request/response traffic across the services.
+
+This documentation describes how to set up the AWS Gateway API Controller, provides example use cases, development concepts, and API references.
 
-This document describes how to set up the AWS Gateway API Controller and provides example use cases.
 With the controller deployed and running, you will be able to manage services for multiple Kubernetes clusters and other targets on AWS through the following:
 
 * **CLI**: Use `aws` and `eksctl` to create clusters and set up AWS policies. Then use `kubectl` and YAML files to set up Kubernetes objects.
@@ -15,10 +21,3 @@ It does this by integrating with the Kubernetes Gateway API.
 This lets you work with Kubernetes service-related resources using Kubernetes APIs and custom resource definitions (CRDs) defined by the Kubernetes [networking.k8s.io specification](https://gateway-api.sigs.k8s.io/references/spec/).
 
 For more information on this technology, see [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/). 
-
-A few things to keep in mind:
-
-* If you are new to the VPC Lattice service, keep in mind that names you use for objects must be unique across your entire account and not just across each cluster used by that account.
-* Your AWS VPC CNI must be v1.8.0 or later to work with VPC Lattice.
-
-