[EKS][AWS Load Balancer Controller Documentation]
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
**Which service(s) is this request for?**
This could be EKS
In this documentation https://docs.aws.amazon.com/eks/latest/userguide/lbc-manifest.html#lbc-install,
In step 3. 2.a, line "sed -i.bak -e '764,773d' ./v2_14_1_full.yaml"
It remove extra "---" from v2_14_1_full.yaml so the above command trying to remove lines from 764 to 773 is incorrect and should be modified as below:
"sed -i.bak -e '764,772d' ./v2_14_1_full.yaml"
or
"sed -i.bak -e '765,773d' ./v2_14_1_full.yaml"
Issue: If we use the command as it is then we are getting below error while applying the manifest file v2_14_1_full.yaml.
The request is invalid: patch: Invalid value: "map[metadata:map[annotations:map[kubectl.kubernetes.io/last-applied-configuration:{\"apiVersion\":\"rbac.authorization.k8s.io/v1\",\"kind\":\"Role\",\"metadata\":{\"annotations\":{},\"labels\":{\"app.kubernetes.io/name\":\"aws-load-balancer-controller\"}
So, please fix it in document.
**Are you currently working around this issue?**
How are you currently solving this problem?
The issue is fixed by using below command:
"sed -i.bak -e '764,772d' ./v2_14_1_full.yaml"
Contributor guide
Research direction
Open the EKS user guide at the linked load balancer controller installation step and inspect the referenced v2_14_1_full.yaml manifest. Verify the documented sed range against the manifest's separator lines, update the documentation, and confirm that applying the resulting manifest no longer produces the reported patch error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100