Skip to content

Update guide - Update Kubernetes / EKS integration instructions #213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
luisffc opened this issue Nov 22, 2024 · 2 comments · May be fixed by #214
Closed

Update guide - Update Kubernetes / EKS integration instructions #213

luisffc opened this issue Nov 22, 2024 · 2 comments · May be fixed by #214
Assignees

Comments

@luisffc
Copy link

luisffc commented Nov 22, 2024

Guide to be updated
https://turbot.com/guardrails/docs/guides/kubernetes/import-kubernetes-cluster#cluster-name

Reason for update
Guardrails agent requires additional configuration on EKS node to be able to retrieve the cluster name from tag

Proposed changes
Add a note saying the instance metadata HttpPutResponseHopLimit should be set to 2 or greater

@luisffc luisffc added the documentation Improvements or additions to documentation label Nov 22, 2024
@luisffc luisffc self-assigned this Nov 22, 2024
luisffc added a commit that referenced this issue Nov 22, 2024
@rajlearner17 rajlearner17 added guide and removed documentation Improvements or additions to documentation labels Dec 6, 2024
Copy link

github-actions bot commented Feb 4, 2025

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Feb 4, 2025
Copy link

github-actions bot commented Mar 6, 2025

This issue was closed because it has been stalled for 90 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants