orange-tailor-85423
05/01/2019, 6:14 PMdamp-book-35965
05/01/2019, 8:04 PMignoreChanges
works ?strong-belgium-23055
05/01/2019, 8:09 PMearly-musician-41645
05/01/2019, 9:44 PMrefresh
on an AWS stack and was logged into the wrong account. For some reason I said "yes, delete all those things from my state" before realizing the mistake.
Is there a way to recover a previous state, e.g. from yesterday or from before the last refresh?fierce-dinner-20116
05/01/2019, 10:29 PMv.0.7.2
of cert-manager
via Pulumi https://github.com/jetstack/cert-manager/releases/tag/v0.7.2 ? (I’m trying to deploy 0.7.2, but I’ve seen this issue with v.0.7.0
).
Whenever I run pulumi up
with the certManager
k8s.yaml.ConfigGroup
, I get this error:
kubernetes:apiregistration:APIService (<http://v1beta1.admission.certmanager.k8s.io|v1beta1.admission.certmanager.k8s.io>):
error: failed to determine if the following GVK is namespaced: apiregistration/v1beta1, Kind=APIService
kubectl apply --dry-run -f cert-manager.yaml
doesn’t complain at all.dry-garden-50738
05/02/2019, 6:47 AMawsx
https://github.com/pulumi/pulumi-awsx/pull/262 🙂 do I have to sign a CLM or anything to get it merged?cold-coat-35200
05/02/2019, 1:13 PMnew aws.ec2.VolumeAttachment(`wordpress-content-attachment`, {
instanceId: ec2Instance.id,
volumeId: dataVolume.id,
deviceName: '/dev/xvdc',
forceDetach: true
})
When something changed in the instance, it will trigger a volume attachment replace too.
You can see in the code sample how it's handled by pulumi, nothing changed in the code between the commands.
Basically first it's say that volume in use, looks like it ignores forceDetach, then the second time realizes, that it's detached from the previous one, therefore unable to detach it and after a refresh everything is good.
Is it normal?gorgeous-egg-16927
05/02/2019, 5:06 PMpowerful-london-34081
05/02/2019, 5:27 PMmagnificent-businessperson-11122
05/02/2019, 8:22 PMicy-dress-83371
05/02/2019, 9:27 PMcould not create stack: An IO error occurred during the current operation: blob (code=Unknown): MissingRegion: could not find region configuration
gray-elephant-37695
05/03/2019, 6:26 AMdry-garden-50738
05/03/2019, 3:31 PMserverless-offline
offers?dry-garden-50738
05/03/2019, 3:31 PMquick-action-34599
05/03/2019, 3:48 PMquick-action-34599
05/03/2019, 3:48 PMmillions-judge-24978
05/03/2019, 6:35 PMfierce-dinner-20116
05/03/2019, 9:09 PM// Make the 'frontend' Service public by setting it to be of type
// LoadBalancer
if (obj.kind == "Service" && obj.metadata.name == "frontend") {
if (obj.spec) {
obj.spec.type = "LoadBalancer"
}
}
Is there a way to just tell the compiler that obj
is a k8s Service
, and just assign obj.spec.type=Loadbalancer directly without needing to check to see if spec
is a field on obj
at all?quick-action-34599
05/03/2019, 10:19 PMquick-action-34599
05/03/2019, 10:20 PMquick-action-34599
05/03/2019, 10:20 PMshy-army-45455
05/04/2019, 7:41 AMstrong-belgium-23055
05/04/2019, 12:57 PMadamant-intern-63433
05/04/2019, 5:54 PMerror: YAMLException: bad indentation of a mapping entry at line 47, column 9:
- 1.1.1.1
^
with the values
config below.
// `<https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-config>`
new k8s.helm.v2.Chart("certmanager",
{
...
values: {
podDnsPolicy: "None",
podDnsConfig: {
nameservers: ["1.1.1.1", "8.8.8.8"]
}
}
},
{ providers: { kubernetes: this.k8sProvider } });
This seems to be about underlying yaml parser of the module or I'm trying to set the values in a wrong way and missing something very basic here. Has anyone bumped into anything similar before?orange-policeman-59119
05/04/2019, 7:13 PM.Values.podDnsConfig.nameservers
is referenced in the chart?glamorous-printer-14057
05/05/2019, 3:55 PM0.0.0.0/0
which is clearly not production-ready.
I also saw instructions here https://pulumi.io/reference/pkg/nodejs/@pulumi/gcp/sql/#private-ip-instance, but this ends up creating a new Cloud SQL VPC separate from default
. Is the best path to do this and then set up VPC peering with my GKE VPC?gentle-diamond-70147
05/05/2019, 3:59 PMPrivate services access is implemented as a VPC peering connection between your VPC network and the Google services VPC network where your Cloud SQL instance resides.
shy-army-45455
05/06/2019, 4:45 AM${v}
), but to not avail. Any tips?dry-garden-50738
05/06/2019, 7:00 AMdry-garden-50738
05/06/2019, 7:00 AM