cold-coat-35200
10/29/2018, 9:33 AMorange-tailor-85423
10/29/2018, 6:53 PMorange-tailor-85423
10/29/2018, 6:54 PMorange-tailor-85423
10/29/2018, 8:24 PMorange-tailor-85423
10/29/2018, 8:25 PMorange-tailor-85423
10/29/2018, 8:26 PMorange-tailor-85423
10/29/2018, 8:29 PMorange-tailor-85423
10/29/2018, 8:29 PMorange-tailor-85423
10/29/2018, 8:29 PMearly-musician-41645
10/29/2018, 8:34 PMTypes of property 'instanceType' are incompatible.
Type '"m5.xlarge"' is not assignable to type '"c3.2xlarge" | "c3.4xlarge" | "c3.8xlarge" | "c3.large" | "c3.xlarge" | "c4.2xlarge" | "c4.4xlarge" | "c4.8xlarge" | "c4.large" | "c4.xlarge" | "d2.2xlarge" | "d2.4xlarge" | ... 47 more ... | undefined'.
early-musician-41645
10/29/2018, 8:37 PMm5
instance types to @pulumi/aws/ec2/instanceType.d.ts
?early-musician-41645
10/29/2018, 9:01 PM$ pulumi up
Previewing update (poc):
Type Name Plan
pulumi:pulumi:Stack eks-cluster-poc
├─ eks:index:Cluster online-sandbox-pulumi-poc-eks-cluster
+ │ ├─ kubernetes:<http://storage.k8s.io:StorageClass|storage.k8s.io:StorageClass> online-sandbox-pulumi-poc-eks-cluster-gp2 create
+ │ ├─ aws:ec2:SecurityGroupRule online-sandbox-pulumi-poc-eks-cluster-eksClusterIngressRule create
...
Type Name Status Info
pulumi:pulumi:Stack eks-cluster-poc
├─ eks:index:Cluster online-sandbox-pulumi-poc-eks-cluster
+ │ ├─ kubernetes:<http://storage.k8s.io:StorageClass|storage.k8s.io:StorageClass> online-sandbox-pulumi-poc-eks-cluster-gp2 **creating failed** 1 error
+ │ └─ aws:ec2:SecurityGroupRule online-sandbox-pulumi-poc-eks-cluster-eksClusterIngressRule created
+ └─ aws:ec2:SecurityGroupRule ssh-ingress created
Diagnostics:
kubernetes:<http://storage.k8s.io:StorageClass|storage.k8s.io:StorageClass> (online-sandbox-pulumi-poc-eks-cluster-gp2):
error: Plan apply failed: unable to fetch resource description for <http://storage.k8s.io/v1|storage.k8s.io/v1>: Get <https://C8A29503A514BB2E580F0CFA2959B7EF.sk1.us-west-2.eks.amazonaws.com/apis/storage.k8s.io/v1>: getting token: exec: exec: "aws-iam-authenticator": executable file not found in $PATH
Resources:
2 changes
+ 2 created
19 unchanged
Duration: 3.48585638s
Permalink: <https://app.pulumi.com/eshamay/poc/updates/7>
error: update failed
Did I miss that in the docs?early-musician-41645
10/29/2018, 10:18 PMaws-iam-authenticator
issue and just installed it locally. However, now I'm hitting an error during eks.Cluster
creation timing out while creating the kubernetes-dashboard.
Do you want to perform this update? yes
Updating (poc):
Type Name Status Info
pulumi:pulumi:Stack eks-cluster-poc
└─ eks:index:Cluster online-sandbox-pulumi-poc-eks-cluster
+ ├─ kubernetes:<http://storage.k8s.io:StorageClass|storage.k8s.io:StorageClass> online-sandbox-pulumi-poc-eks-cluster-gp2 created
+ ├─ kubernetes:core:ConfigMap online-sandbox-pulumi-poc-eks-cluster-nodeAccess created
+ ├─ aws:cloudformation:Stack online-sandbox-pulumi-poc-eks-cluster-nodes created
+ ├─ pulumi:providers:kubernetes online-sandbox-pulumi-poc-eks-cluster-provider created
+ ├─ kubernetes:core:ServiceAccount online-sandbox-pulumi-poc-eks-cluster-eks-admin created
+ ├─ kubernetes:<http://rbac.authorization.k8s.io:ClusterRoleBinding|rbac.authorization.k8s.io:ClusterRoleBinding> online-sandbox-pulumi-poc-eks-cluster-eks-admin created
└─ kubernetes:yaml:ConfigGroup online-sandbox-pulumi-poc-eks-cluster-dashboard
+ ├─ kubernetes:core:ServiceAccount kube-system/heapster created
+ ├─ kubernetes:core:Secret kube-system/kubernetes-dashboard-certs created
+ ├─ kubernetes:core:ServiceAccount kube-system/kubernetes-dashboard created
+ ├─ kubernetes:<http://rbac.authorization.k8s.io:ClusterRoleBinding|rbac.authorization.k8s.io:ClusterRoleBinding> heapster created
+ ├─ kubernetes:<http://rbac.authorization.k8s.io:RoleBinding|rbac.authorization.k8s.io:RoleBinding> kube-system/kubernetes-dashboard-minimal created
+ └─ kubernetes:core:Service kube-system/kubernetes-dashboard **creating failed** 1 error
Diagnostics:
kubernetes:core:Service (kube-system/kubernetes-dashboard):
error: Plan apply failed: Timeout occurred for 'kubernetes-dashboard'
Resources:
11 changes
+ 11 created
22 unchanged
Duration: 11m16.35025328s
Permalink: <https://app.pulumi.com/eshamay/poc/updates/9>
error: update failed
I retried pulumi up
but got this error:
Updating (poc):
Type Name Status Info
pulumi:pulumi:Stack eks-cluster-poc
└─ eks:index:Cluster online-sandbox-pulumi-poc-eks-cluster
└─ kubernetes:yaml:ConfigGroup online-sandbox-pulumi-poc-eks-cluster-dashboard
+ └─ kubernetes:core:Service kube-system/kubernetes-dashboard **creating failed** 1 error
Diagnostics:
kubernetes:core:Service (kube-system/kubernetes-dashboard):
error: Plan apply failed: services "kubernetes-dashboard" already exists
This seems to be blocking further updates to the stackearly-musician-41645
10/29/2018, 10:18 PMearly-musician-41645
10/29/2018, 10:19 PMhelm upgrade -i
but instead doing a helm install
and failing because it already exists... ??early-musician-41645
10/29/2018, 10:26 PMhelm repo add my-repo <s3://my-helm-repo/charts>
.
Given the example service deployment (copied below) how do I specify custom repo endpoints using the S3 plugin?
// Sample copied from <https://github.com/pulumi/examples/blob/master/kubernetes-ts-helm-wordpress/index.ts>
// Deploy the latest version of the stable/wordpress chart.
const wordpress = new k8s.helm.v2.Chart("wpdev", {
repo: "stable",
version: "2.1.3",
chart: "wordpress"
});
orange-tailor-85423
10/29/2018, 10:32 PMorange-tailor-85423
10/29/2018, 10:33 PMearly-musician-41645
10/29/2018, 11:03 PMpulumi up
it says:
Diagnostics:
kubernetes:core:ConfigMap (kube-system/online-splunk-config):
error: Unable to read kubectl config: invalid configuration: no configuration has been provided
Obviously the kubeconfig doesn't yet exist because the cluster isn't created. Once the cluster is created I need to write out the kubeconfig, copy it somewhere, then configure the local helm to use it.
Is there an example of this workflow?glamorous-printer-66548
10/29/2018, 11:08 PMcacheFrom
almost impossible. In order to effectively use cacheFrom
I need some stable tag (i.e. latest
) or some other identifier that can be derived from logic in the code before the build runs. Prior to your change I was adding latest
as tag to all images which in conjunction with cacheFrom: true
enabled quite good caching. Any thoughts how I can achieve good caching now?quaint-queen-37896
10/30/2018, 12:54 AMOn 11/02 we'll start billing your card on file, ending in XXXX, $0.00 per year.
quaint-queen-37896
10/30/2018, 12:55 AMglamorous-printer-66548
10/30/2018, 1:27 AMDeployments
and Services
one-by-one instead of concurrently. I’m not sure if this previously also the case, but I guess not. Versions: pulumi CLI 0.16.1 , @pulumi/pulumi: 0.16.2
, @pulumi/kubernetes: 0.17.3
.acoustic-candle-40090
10/30/2018, 5:14 AMquick-action-34599
10/30/2018, 12:46 PMquick-action-34599
10/30/2018, 1:36 PMdbSubnetGroupName: subnet.tags.apply((t: any) => t.Name),
quick-action-34599
10/30/2018, 1:46 PMquick-action-34599
10/30/2018, 1:50 PMError authorizing security group ingress: InvalidParameterValue: VPC DB Security Groups cannot be modified with this API version. Please use an API version between 2012-01-15 and 2012-10-31 to modify this group.
😞quick-action-34599
10/30/2018, 2:38 PMquick-action-34599
10/30/2018, 2:38 PM