https://pulumi.com
Join Slack
This message was deleted.
s

Slackbot

over 2 years ago
This message was deleted.
s
l
+2
  • 4
  • 5
  • 284
Hey good morning. We are currently storing our pulumi file in an S3 bucket. This bucket is encrypted...
f

Fredrick

over 1 year ago
Hey good morning. We are currently storing our pulumi file in an S3 bucket. This bucket is encrypted using a KMS key. When running
pulumi login <s3://mybucket>
I get this error: error: problem logging in: read ".pulumi/meta.yaml": blob (key ".pulumi/meta.yaml") (code=Unknown): AccessDenied: Access Denied status code: 403, request id: 8N5AVCW0D0CF17DY, host id: VsmKrytuAAGUIU+pdQ6ZrikCcdD7uGxRru7oauhI+MOgIijUlWxp4YnNtRDptX9c4Z02GSvDcXA= Im assuming its because the access key that im using needs permissions updated..If this is the case what IAM permissions are needed to perform this ?
f
k
  • 2
  • 1
  • 282
This message was deleted.
s

Slackbot

about 3 years ago
This message was deleted.
s
f
+2
  • 4
  • 4
  • 282
This message was deleted.
s

Slackbot

over 2 years ago
This message was deleted.
s
c
+2
  • 4
  • 16
  • 279
Hey, Using EKS and metrics-server(from the helm chart) I have this error, I created the cluster usin...
a

Aymeric Beudaert

about 1 year ago
Hey, Using EKS and metrics-server(from the helm chart) I have this error, I created the cluster using the pulumi guide with EKS and node groups. I have the aws-node, with the CNI installed (but not the addon)
E0729 17:05:11.585565       1 scraper.go:149] "Failed to scrape node" err="Get \"<https://10.0.12.191:10250/metrics/resource>\": remote error: tls: internal error" node="ip-10-0-12-191.us-west-2.compute.internal"
E0729 17:05:46.982621       1 scraper.go:147] "Failed to scrape node, timeout to access kubelet" err="Get \"<https://10.0.158.73:10250/metrics/resource>\": context deadline exceeded" node="ip-10-0-158-73.us-west-2.compute.internal" timeout="10s"
I have other deployment working fine, Also I can use HPA with CPU based autoscaling. But I have random warning in the cluster by the HPA (failed to get cpu utilization: unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)\
a
r
  • 2
  • 2
  • 278
This message was deleted.
s

Slackbot

over 4 years ago
This message was deleted.
s
m
b
  • 3
  • 3
  • 276
This message was deleted.
s

Slackbot

over 5 years ago
This message was deleted.
s
n
+2
  • 4
  • 9
  • 276
This message was deleted.
s

Slackbot

about 3 years ago
This message was deleted.
s
a
j
  • 3
  • 3
  • 275
This message was deleted.
s

Slackbot

over 2 years ago
This message was deleted.
s
j
j
  • 3
  • 2
  • 274
This message was deleted.
s

Slackbot

about 3 years ago
This message was deleted.
s
j
c
  • 3
  • 2
  • 274
Previous121314Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by