gistfile1.txt

Tor Fredrik Eriksen [8:08 PM] 
So I am getting a new error now
```Exception ( Monitor Deploy )
Failure executing: PATCH at: https://schip-sandbox.cre-pro.schibsted.io/apis/extensions/v1beta1/namespaces/default/deployments/rocketlogsapi. Message: jsonpatch add operation does not apply: doc is missing path: /spec/template/spec/containers/0/env/0. Received status: Status(apiVersion=v1, code=500, details=null, kind=Status, message=jsonpatch add operation does not apply: doc is missing path: /spec/template/spec/containers/0/env/0, metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=null, status=Failure, additionalProperties={}).```

[8:10]  
https://pipeline.schibsted.io/#/applications/rocketlogsapi/executions/136eca5f-e5fa-498f-a602-82b52d4fc200?stage=0&step=0&details=deploymentConfig

Fabian Selles Rosa [8:15 PM] 
its a known bug

Tor Fredrik Eriksen [8:15 PM] 
ok


----- Today February 3rd, 2017 -----
Tor Fredrik Eriksen [11:24 AM] 
I guess i will just abandon logs-api then and start work on chat-api

[11:24]  
Is anyone working on this bug?

[11:24]  
will i run into it on chat-api again?

[11:24]  
I feels like the spinnaker and kubernetes stuff is really half baked

[11:25]  
Is there a way for me to just spin up the CRE kubernetes cluster in one of our environments and figure this stuff out myself?

[11:25]  
Without spinnaker messing up the workflow

[11:26]  
infact all I need is the kube2iam stuff and I can spin up one of the kubernetes cluster guides found on the internet

Audun Fauchald Strand [11:27 AM] 
If you have kubectl access, and you should, you can do the initial deploy using that, probably

Fabian Selles Rosa [11:28 AM] 
@torfredrik this bug has been fixed afaik

[11:28]  
probably last version is not version

[11:28]  
i willc hase it with delivery, more importantly this usually not happens

[11:28]  
so you can work as before it happens sometimes when updates the deployment object

Tor Fredrik Eriksen [11:33 AM] 
How do i get kubectl access?

Audun Fauchald Strand [11:35 AM] 
https://confluence.schibsted.io/display/SPTINF/Sandbox+Cluster

new messages
Tor Fredrik Eriksen [11:37 AM] 
So given that I can deploy to CRE using kubectl, why even use spinnaker for this? Can’t we just create a gradle plugin for k8s leveraging kubectl and move our service config to k8s in our projects sidestepping spinnaker completely?

Oliver Soell [11:39 AM] 
yes, you could do that

[11:39]  
however spinnaker does give you the ability to do health checks and make sure that your new code is working before you tear down the old code (or just disable it via blue-green)

Audun Fauchald Strand [11:41 AM] 
the long term plan, has been to make spinnaker use config from the repo, and call an api in the cluster for deploying. This is not supported by spinnaker yet