billions-glass-17089
08/15/2022, 7:12 PMenableServerSideApply: true
flag to my provider and then ran pulumi preview
and I got this error:
kubernetes:<http://elasticsearch.k8s.elastic.co/v1:Elasticsearch|elasticsearch.k8s.elastic.co/v1:Elasticsearch> (family):
error: error reading from server: EOF
Seems like it's not working with ECK (which I installed via k8s.yaml.ConfigGroup
calm-iron-40008
08/17/2022, 2:33 AMbright-horse-50102
08/19/2022, 9:38 PMfew-pillow-1133
08/20/2022, 4:01 PMException: Cannot read properties of null (reading 'data')
error: TypeError: Cannot read properties of null (reading 'data')
at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/cluster.ts:580:103
at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/output.ts:383:31
at Generator.next (<anonymous>)
at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:21:71
at new Promise (<anonymous>)
at __awaiter (/root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:17:12)
at applyHelperAsync (/root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:229:12)
at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/output.ts:302:65
at processTicksAndRejections (node:internal/process/task_queues:96:5)
error: an unhandled error occurred: Program exited with non-zero exit code: 1
victorious-dusk-75271
08/21/2022, 9:38 PMvictorious-dusk-75271
08/21/2022, 9:41 PMserviceAccount.create: false
but its not picking up
https://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller
i have tried both { serviceAccount: { create: false }} and 'serviceAccount.create': falsebored-spoon-83710
08/23/2022, 6:17 PMmillions-judge-24978
08/23/2022, 6:58 PMk8s.Provider
for an existing EKS cluster? I would like to be able to do something like eks.getClusterOutput({...}).provider
, as I would be able to if I had just created with new eks.Cluster({...}).provider
. Failing that, at least how I can generate the kubeconfig
file text from eks.getClusterOutput().something
.victorious-church-57397
08/24/2022, 2:08 PMunable to run program: Error: unknown resource type 'kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>'
on pcl-087019550.pp line 0:
1: resource "github_actions_runner_operatorRunner_poolGithubActionRunner" "kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>" {
unknown resource type 'kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>'
Is there anything i can do locally to get the program to recognise the resource type? I'm installing the CRDs etc using helm, but need to deploy the actual deployment separatelybright-horse-50102
08/25/2022, 1:54 AMWaiting for StatefulSet update to roll out (0/n Pods ready)
2. If you do update the pods yourself while Pulumi is waiting, Pulumi will continue to wait on Waiting for StatefulSet update to roll out (n/n Pods ready)
, and eventually error and time out because .status.currentRevision
was not updated to .status.updatedRevision
:
Diagnostics:
kubernetes:apps/v1:StatefulSet (interactions-app):
error: 3 errors occurred:
* the Kubernetes API server reported that "default/interactions-app-b2ecafa3" failed to fully initialize or become live: 'interactions-app-b2ecafa3' timed out waiting to be Ready
* 32 out of 32 replicas succeeded readiness checks
* StatefulSet controller failed to advance from revision "interactions-app-b2ecafa3-646dcff454" to revision "interactions-app-b2ecafa3-569b7cb476"
Relevant issue? https://github.com/pulumi/pulumi-kubernetes/issues/1066victorious-dusk-75271
08/25/2022, 9:20 AMscheme
in in spec? typescript is complaining about it
apiVersion: elbv2.k8s.aws/v1beta1
kind: IngressClassParams
metadata:
name: awesome-class
spec:
scheme: internal
ipAddressType: dualstack
tags:
- key: org
value: my-org
victorious-church-57397
08/26/2022, 3:14 PMCustomResource
to try and deploy an instance of the resource which is configured on the cluster with the helm chart. I've got pulumi creating it, and it all looks good but no pods are actually being deployed, if i manually run kubectl apply -f
on the yaml file, then it works fine but not when ive converted it to a JS object format, cant help but thinking the CustomResource
might not be what im after?bored-spoon-83710
08/27/2022, 3:13 PMincalculable-midnight-8291
08/30/2022, 4:18 PMk8s.helm.v3.Release
so that pulumi skips uninstall on a stack destroy, where the cluster itself will be taken down?victorious-dusk-75271
08/30/2022, 8:54 PMwarning: Refreshed resource is in an unhealthy state:
* Resource 'allrites-frontend' was created but failed to initialize
* Service does not target any Pods. Selected Pods may not be ready, or field '.spec.selector' may not match labels on any Pods
fierce-pillow-7950
08/31/2022, 12:40 AMincalculable-midnight-8291
08/31/2022, 10:38 AMk8s.core.v1.Servic
type LoadBalancer has got its external ip assigned?
Edit: found it!
const externalIP = service.status.loadBalancer.ingress;
It will be an array though.ripe-shampoo-80285
08/31/2022, 9:06 PMvictorious-exabyte-70545
08/31/2022, 11:49 PMripe-russia-4239
09/01/2022, 11:25 AMfailed to pull chart: looks like "<oci://myregistry.azurecr.io/helm/mychart>" is not a valid chart repository or cannot be reached: object required
brash-gigabyte-81569
09/01/2022, 5:22 PMfull-boots-69133
09/05/2022, 10:35 PMclient-go
to >1.23.x
.
I guess the question is, how does pulumi decide which resource plugin version it requires?future-student-37410
09/06/2022, 8:32 AM{
ApiVersion = "apps/v1",
Kind = "Deployment",
Metadata = new ObjectMetaArgs
{
Name = "redis-deployment",
Labels =
{
{ "app", "redis" },
},
},
Spec = new DeploymentSpecArgs
{
Replicas = 1,
Selector = new LabelSelectorArgs
{
MatchLabels =
{
{ "app", "redis" },
},
},
Template = new PodTemplateSpecArgs
{
Metadata = new ObjectMetaArgs
{
Labels =
{
{ "app", "redis" },
},
Annotations =
{
{ "<http://dapr.io/enabled|dapr.io/enabled>", "true" },
{ "<http://dapr.io/app-id|dapr.io/app-id>", "redis" },
{ "<http://dapr.io/app-port|dapr.io/app-port>", "6379" },
{ "<http://dapr.io/enable-api-logging|dapr.io/enable-api-logging>", "true" }
},
},
Spec = new PodSpecArgs
{
Containers =
{
new ContainerArgs
{
Name = "redis-message-broker",
Image = "<http://registry.hub.docker.com/library/redis:latest|registry.hub.docker.com/library/redis:latest>",
ImagePullPolicy = "Always",
},
},
},
},
},
}, new CustomResourceOptions()
{
Parent = this
});
How do I get the Redis secret key out of this deployment?
The other problem is, that I don't know how to translate the dapr component yaml file into Pulumi resources. The Pulumi converter throws an error saying it is not able to convert. The yaml file looks like this:
apiVersion: <http://dapr.io/v1alpha1|dapr.io/v1alpha1>
kind: Component
metadata:
name: pubsub
namespace: default
spec:
type: pubsub.redis
version: v1
metadata:
- name: redisHost
value: <REPLACE WITH HOSTNAME FROM ABOVE - for Redis on Kubernetes it is redis-master.default.svc.cluster.local:6379>
- name: redisPassword
secretKeyRef:
name: redis
key: redis-password
# uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache)
# - name: enableTLS
# value: true
source: https://docs.dapr.io/getting-started/tutorials/configure-state-pubsub/#next-steps
Did anyone of you deploy the Dapr Pub/Sub with Redis already?victorious-dusk-75271
09/06/2022, 12:07 PMvictorious-dusk-75271
09/06/2022, 12:20 PMvictorious-dusk-75271
09/06/2022, 10:17 PM@pulumi/eks
?victorious-dusk-75271
09/07/2022, 3:48 PMbig-potato-91793
09/07/2022, 11:28 PMvictorious-dusk-75271
09/09/2022, 4:27 AMkubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (primary-eks-fluent-bit):
warning: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "<https://xxx/openapi/v2?timeout=32s>": dial tcp: lookup xxxxxxx on 172.22.160.1:53: read udp 172.22.161.178:34533->172.22.160.1:53: i/o timeout
error: Preview failed: failed to read resource state due to unreachable cluster. If the cluster has been deleted, you can edit the pulumi state to remove this resource
does anyone know how to remove those? removing those causes problem with dependency and take a lot of time to fix IaCvictorious-dusk-75271
09/09/2022, 5:15 AMvictorious-dusk-75271
09/09/2022, 5:15 AM