mammoth-afternoon-82670
09/30/2020, 6:56 PM--target
into the digitalocean.KubernetesCluster
, which brought a new kubeconfig content, but for some reason it doesn't seem to be used by the provider at all. Still getting configured Kubernetes cluster is unreachable: unable to load schema information from the API server: the server has asked for the client to provide credentials
flat-insurance-25294
10/01/2020, 8:58 AMloud-battery-37784
10/01/2020, 1:57 PMloud-battery-37784
10/01/2020, 1:58 PMloud-battery-37784
10/01/2020, 2:01 PMflat-insurance-25294
10/01/2020, 6:21 PMpulumi up
runs and the only thing that has changed is the replica count in index.ts
(written using Pulumi APIs) then it shouldn’t really build the docker image again.
But what bothers me is how unclear it is right now.bitter-application-91815
10/01/2020, 6:25 PMbitter-application-91815
10/01/2020, 6:25 PMbitter-application-91815
10/01/2020, 6:25 PMbitter-application-91815
10/01/2020, 6:25 PMflat-insurance-25294
10/01/2020, 6:26 PMts
export const image = repo.buildAndPushImage("./app");
Running this twice where ./app
hasn’t changed since last time, should be no-op the second time and re-used the image already pushed since last time.
I’d consider it a bug, not sure if I should post an issue, though.flat-insurance-25294
10/01/2020, 6:29 PMbuildAndPushImage
This way I should technically get what I want - where the only “new” thing is the replica count, while the image stays the same.
Depending on how Pulimi does its kubectl
command where the only “new” thing should be the replica count.loud-battery-37784
10/01/2020, 6:33 PMif/else
block and do work.loud-battery-37784
10/01/2020, 6:34 PMflat-insurance-25294
10/01/2020, 6:42 PMreplica
count then that’s the only thing I want to change.
Docker today already has the concept of layer hash. If no layer has changed, then that means no new image is necessary.broad-dog-22463
10/01/2020, 6:50 PMbroad-dog-22463
10/01/2020, 6:50 PMbroad-dog-22463
10/01/2020, 6:51 PMflat-insurance-25294
10/01/2020, 9:00 PMpulumi up
a second time where replica
number has changed, how does it make sure it’s not using a new image when using buildAndPushImage
?broad-dog-22463
10/01/2020, 9:03 PMbroad-dog-22463
10/01/2020, 9:03 PMbroad-dog-22463
10/01/2020, 9:04 PMbroad-dog-22463
10/01/2020, 9:04 PMflat-insurance-25294
10/01/2020, 9:05 PMbranch_names:latest
for everything except master
& develop
With separate repositories for each branch.
develop
and master
branches share the same repository.
develop
will use automated commit sha
as a tag.
master
will use hand selected (manual typed) commit sha
as image tag from the same ECR/Docker repository as develop
.flat-insurance-25294
10/01/2020, 9:10 PMconst image = buildAndPushImage(name: "app:23", pathOrBuild: "./app"): RepositoryImage
or
const image = new RepositoryImage(repository: repo, image: "app:23")
?
if I want to get a specific image
or build it, if it’s missing.broad-dog-22463
10/01/2020, 9:11 PMflat-insurance-25294
10/01/2020, 9:11 PMbroad-dog-22463
10/01/2020, 9:12 PMbroad-dog-22463
10/01/2020, 9:12 PMflat-insurance-25294
10/01/2020, 9:13 PMflat-insurance-25294
10/01/2020, 9:13 PM