Open RaviVadera opened 2 months ago
@rquitales Were you able to repro the issue? What is your feedback on it?
This issue was created alongside #1133 and relates to accessing the cluster's API Server to perform on-cluster actions. As the cluster does not have a public endpoint, our provider will be unable to perform these actions. This could potentially be resolved with: #1027 as this will defer the auth setup to be handled by AWS.
Thank you. What is this issue (1134) tracking then?
1133 tracks disabling the health checking. This issue (1134) tracks the AWS auth related configmap updates required on cluster. As the cluster is private, we can't update the configmap currently.
I just wanted to point to this issue as well https://github.com/pulumi/pulumi-eks/issues/1191. would be great if they can all be fixed together. I think just respecting the proxy config should do the trick for the time being
What happened?
When creating a
eks.Cluster
with only private endpoint enabled, aws-auth resource fails to be created and results in resource creation failWhat happened Pulumi fails with,
Expected to happen Pulumi shold not create the config map resource, in case of only private API endpoint enabled.
Example
Create a cluster with following params,
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).