DOC-399: Document Kubernetes endpoint injection - #871
Conversation
Explain workload opt-in behavior, certificate management, and EKS Auto Mode so users can configure transparent LocalStack access safely.
Deploying localstack-docs with
|
| Latest commit: |
14f91f8
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2c81a644.localstack-docs.pages.dev |
| Branch Preview URL: | https://doc-399-doc-k8s-operator-tra.localstack-docs.pages.dev |
simonrw
left a comment
simonrw
left a comment
There was a problem hiding this comment.
Looks really good thanks! Just a couple of minor points
| The `dnsConfigName` and `dnsConfigNamespace` fields remain required by the `LocalStack` resource schema, but the Operator does not use their values in `eksauto` mode. | ||
| Use opt-in [endpoint injection](#inject-localstack-endpoints-into-workloads) to configure workloads that need to access LocalStack. |
There was a problem hiding this comment.
We should really update this!
There was a problem hiding this comment.
What do we update and what should we update it to? :)
There was a problem hiding this comment.
No I mean this is weird behaviour in the operator. Why should the user set values which do not apply to eksauto mode when running in eksauto mode. I don't think it's a huge problem right now, but the we in this context is @localstack/deployx - the operator maintainers.
- Consolidate the dnsPolicy/nameserver/search-domain/ndots bullets into one higher-level explanation that also reassures readers LocalStack only intercepts domains it owns (localhost.localstack.cloud or $LOCALSTACK_HOST) and forwards everything else to the cluster DNS resolver as normal. - Drop the cert-manager SelfSigned-issuer trust-anchor explanation as unnecessary cert-manager implementation detail for the operator docs.
|
Thanks @simonrw — pushed Left the EKS Auto Mode comment ("We should really update this!") unaddressed for now — wasn't clear whether that's about the docs wording or the |
|
This looks great, thanks! Happy for this to be merged. I've addressed that comment |
3 participants
Summary
AWS_ENDPOINT_URLinjection for Kubernetes workloads