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:18 AM1) state file contains errors: resource urn:pulumi:staging::allrites-infrastructure::custom:resource:eks$custom:resource:AlbIngressController$aws:iam/role:Role::primary-eks-aws-loadbalancer-controller-role dependency urn:pulumi:staging::allrites-infrastructure::custom:resource:eks$custom:resource:AlbIngressController$kubernetes:core/v1:Namespace::primary-eks-alb-namespace refers to missing resource
2) importing this file could be dangerous; rerun with --force to proceed anyway
victorious-dusk-75271
09/09/2022, 5:19 AMaverage-pilot-3793
09/12/2022, 10:08 AMcoreDns
aws.eks.Addon
with fargate in a k8s. https://www.pulumi.com/registry/packages/aws/api-docs/eks/addon/#sts=Create%20a%20Addon%20Resource the documentation provides some level of information but when applying it i run into the following error. the full kubectl describe command output is in the thread. I suspect the label should be updated in the ResourceOptions somehow to <http://eks.amazonaws.com/fargate-profile=|eks.amazonaws.com/fargate-profile=><cluster name>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 2m29s (x5494 over 3d21h) default-scheduler 0/3 nodes are available: 3 node(s) had taint {<http://eks.amazonaws.com/compute-type|eks.amazonaws.com/compute-type>: fargate}, that the pod didn't tolerate.
most-lighter-95902
09/15/2022, 3:33 PM--from-file
flag in kubectl for secret creation via Pulumi?delightful-bear-69098
09/18/2022, 2:18 PMbored-spoon-83710
09/19/2022, 4:29 PMpulumi up --skip-preview
it works as intended. However, if I do a pulumi up
I get an error during preview:
error: Preview failed: resource kube-system/ebs-csi-node was not successfully created by the Kubernetes API server : DaemonSet.apps "ebs-csi-node" is invalid: [spec.template.metadata.labels: Invalid value: map[string]string(nil): `selector` does not match template `labels`, spec.template.spec.containers: Required value]
Is it a limitation of the provider or did I miss something? Is there a workaround (other than skipping the preview)?brash-gigabyte-81569
09/21/2022, 9:49 PMsome-continent-7311
09/29/2022, 7:40 AM@pulumi/pulumi
and @pulumi/kubernetes
to ^3.0.0
and running pulumi up
I get this warning:
W0929 13:38:59.750875 65229 gcp.go:119] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.26+; use gcloud instead.
To learn more, consult <https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke>
What should I do exactly to get rid of the warning?damp-honey-93158
10/05/2022, 2:36 PMdamp-honey-93158
10/06/2022, 7:15 AMdamp-honey-93158
10/06/2022, 7:16 AMlively-needle-84406
10/06/2022, 2:15 PMexport const istioBaseChart = new k8s.helm.v3.Release("istio-base", {
chart: "base",
version: istioVersion,
namespace: istioNamespace.metadata.name,
repositoryOpts: {
repo: "<https://istio-release.storage.googleapis.com/charts>",
},
}, {
dependsOn: [cluster, istioNamespace]
});
Istiod:
export const istiod = new k8s.helm.v3.Chart("istiod", {
chart: "istiod",
version: istioVersion,
namespace: istioNamespace.metadata.name,
fetchOpts: {
repo: "<https://istio-release.storage.googleapis.com/charts>",
},
}, {
dependsOn: [cluster, istioNamespace, istioBaseChart]
});
The error I am receiving is:
kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (istio-base):
error: could not get server version from Kubernetes: Get "<https://B042EE83435E804CA59AE3C4ACC5C169.sk1.us-west-1.eks.amazonaws.com/version?timeout=32s>": dial tcp: lookup <http://xxxxxxxxxxxxxx.sk1.us-west-1.eks.amazonaws.com|xxxxxxxxxxxxxx.sk1.us-west-1.eks.amazonaws.com> on [xxxx:xxxx:xxx:xxxx::x]:xx: no such host
To me, this looks like the dependency on the cluster and other resources is not being honored. Any ideas how to ensure the cluster and other resources get created properly before applying these charts?