damp-book-35965
04/02/2019, 10:11 PMDiagnostics:
pulumi:pulumi:Stack (xxx):
error: update failed
kubernetes:core:Service (kube-system/prometheus-operator-prometheus):
error: Plan apply failed: 2 errors occurred:
* Resource operation was cancelled for 'prometheus-operator-prometheus'
* Service was not allocated an IP address; does your cloud provider support this?
What's really happening ? There are enough IPs in the VPC to provisioncreamy-potato-29402
04/02/2019, 10:14 PMdamp-book-35965
04/02/2019, 10:15 PMcreamy-potato-29402
04/02/2019, 10:16 PMCancel
RPC call.damp-book-35965
04/02/2019, 10:17 PMkubernetes:helm.sh:Chart prometheus-operator
~ └─ kubernetes:core:Service kube-system/prometheus-operator-prometheus updating.. [2/3] Attempting to allocate IP address to Service
creamy-potato-29402
04/02/2019, 10:17 PMdamp-book-35965
04/02/2019, 10:17 PMcreamy-potato-29402
04/02/2019, 10:17 PMdamp-book-35965
04/02/2019, 10:18 PMcreamy-potato-29402
04/02/2019, 10:22 PMdamp-book-35965
04/02/2019, 10:31 PMcreamy-potato-29402
04/02/2019, 10:31 PMdamp-book-35965
04/02/2019, 10:32 PMcreamy-potato-29402
04/02/2019, 10:32 PMdamp-book-35965
04/02/2019, 10:32 PMcreamy-potato-29402
04/02/2019, 10:33 PMkubectl get
it, is there an IP address reported in the .status
field.damp-book-35965
04/02/2019, 10:33 PMcreamy-potato-29402
04/02/2019, 10:34 PMdamp-book-35965
04/02/2019, 10:34 PMcreamy-potato-29402
04/02/2019, 10:35 PMdamp-book-35965
04/02/2019, 10:36 PMcreamy-potato-29402
04/02/2019, 10:36 PMdamp-book-35965
04/02/2019, 10:36 PMcreamy-potato-29402
04/02/2019, 10:37 PM.status
field with -o yaml
damp-book-35965
04/02/2019, 10:37 PMstatus:
loadBalancer: {}
creamy-potato-29402
04/02/2019, 10:38 PMdamp-book-35965
04/02/2019, 10:41 PMcreamy-potato-29402
04/02/2019, 10:43 PMdamp-book-35965
04/02/2019, 10:43 PMwhite-balloon-205