broad-dog-22463
10/01/2020, 9:19 PMbroad-dog-22463
10/01/2020, 9:20 PMflat-insurance-25294
10/01/2020, 9:27 PMbroad-dog-22463
10/01/2020, 9:28 PMbroad-dog-22463
10/01/2020, 9:28 PMflat-insurance-25294
10/01/2020, 9:28 PMbuildAndPushImage().image()
does when it’s used in conjunction with awsx/kubernetes/EKS
Inside a Deployment/Pod
manifest for containers.
spec: {
containers: [{
image, // **Use the image built above**
}],
I know the string would be something like
<http://012345678901.dkr.ecr.us-west-2.amazonaws.com/my-repo-e2fe830:latest|012345678901.dkr.ecr.us-west-2.amazonaws.com/my-repo-e2fe830:latest>
Where parts of that is based on AWS meta-data like ID, region etc.broad-dog-22463
10/01/2020, 9:29 PMbroad-dog-22463
10/01/2020, 9:29 PMbroad-dog-22463
10/01/2020, 9:29 PMflat-insurance-25294
10/01/2020, 9:31 PM<http://amazonaws.com/my-repo-e2fe830:latest|amazonaws.com/my-repo-e2fe830:latest>
each time.
The newer pods will run a new image if Docker failed to understand that there is no need for a new “image push” - that’s not on Pulumi though.
That can happen for loads of reasons, e.g poorly made Dockerfile, etc.broad-dog-22463
10/01/2020, 9:32 PMflat-insurance-25294
10/01/2020, 9:32 PMflat-insurance-25294
10/01/2020, 9:33 PMflat-insurance-25294
10/01/2020, 9:34 PMbroad-dog-22463
10/01/2020, 9:36 PMquaint-electrician-41503
10/02/2020, 6:37 PMhelm -f values.yaml name /path/to/chart
quaint-electrician-41503
10/02/2020, 6:38 PMvalues.yaml
from LocalChartOpts
. I found kubernetes.yaml
but can't seem to get the proper values from E.G. ConfigFile
quaint-electrician-41503
10/02/2020, 6:41 PMbroad-dog-22463
10/02/2020, 6:42 PMquaint-electrician-41503
10/02/2020, 7:18 PMhelm -f values.yaml name /path/to/chart
which is natural via helm, I cannot IE apply ConfigFile
for the values argument of LocalChartOpts
miniature-leather-70472
10/05/2020, 11:13 AMlimited-rainbow-51650
10/06/2020, 12:49 PM~ kubernetes:apps/v1:Deployment: (update)
[id=deployer-ut11s29w/deployer-activities-k8s-l0dmq9rt]
[urn=urn:pulumi:development::deployer::kubernetes:apps/v1:Deployment::deployer-activities-k8s]
[provider=urn:pulumi:development::deployer::pulumi:providers:kubernetes::default_2_6_1::a73e10a4-562a-40e2-9db1-61bb39736827]
~ spec: {
~ template: {
~ spec: {
~ containers: [
- [0]: {
- args : [
- [0]: "osimis-deploy-activities"
]
- env : [
- [0]: {
- name : "TEMPORAL_FRONTEND_HOST"
- value: "<redacted>"
}
]
- image : "<redacted>"
- imagePullPolicy: "Always"
- livenessProbe : {
- exec : {
- command: [
- [0]: "/bin/sh"
- [1]: "-c"
- [2]: "ps -ef | grep osimis-deploy-activities"
]
}
- failureThreshold : 2
- initialDelaySeconds: 10
- periodSeconds : 10
- successThreshold : 1
- timeoutSeconds : 5
}
- name : "activities-worker"
- readinessProbe : {
- exec : {
- command: [
- [0]: "/bin/sh"
- [1]: "-c"
- [2]: "ps -ef | grep osimis-deploy-activities"
]
}
- failureThreshold : 6
- initialDelaySeconds: 5
- periodSeconds : 10
- successThreshold : 1
- timeoutSeconds : 5
}
- resources : {
- limits : {
- cpu : "0.15"
- memory: "120Mi"
}
- requests: {
- cpu : "0.1"
- memory: "100Mi"
}
}
- volumeMounts : [
- [0]: {
- mountPath: "/etc/pulumi-deployer/osimisdockercreds.conf"
- name : "osimis-docker-hub-credentials"
- subPath : "osimisdockercredes.conf"
}
]
}
]
}
}
}
Resources:
~ 1 to update
8 unchanged
I’m not confident in applying this. What is happening?
Context: Pulumi v2.11.2 + Kubernetes provider 2.6.1limited-rainbow-51650
10/06/2020, 12:49 PMspec
of a Deployment
. That’s the only change, and I’m also the only one working with this stack, with which I want to clarify that no other team member could have made any changes. When I do a preview --diff
, it wants to delete the containers
section of the Pod `spec`:quiet-wolf-18467
k8s.yaml.ConfigFile
or Helm template as straight up YAML in the Pulumi code?quiet-wolf-18467
limited-rainbow-51650
10/07/2020, 11:54 AMpods
resource was not added to list of permissions. Meanwhile, the statefulset and the pods are up and running though. So I redeployed the automation app with more permissions and ran again. But now it bails out complaining that my statefulset already exists. Running pulumi stack export
shows me indeed that my statefulset is not recorded in the state. /cc @gorgeous-egg-16927bitter-application-91815
10/08/2020, 11:07 AMbitter-application-91815
10/08/2020, 11:07 AMbitter-application-91815
10/08/2020, 11:07 AMkubectl get ing -n axiomdb
bitter-application-91815
10/08/2020, 11:08 AM