Matti Paksula

mortar yank to ignore some resources

3

When developing it just handy sometimes to fire+yank in a loop - if you happen to have let'sencrypt certs it is easy to get banned from let's encrypt because you...

patch deployments on every fire

2

currently needs to have some build id or timestamp as a variable to make pods roll

yank does not validate yanks

2

anything is always yanked succesfully

mortar recurse

2

``` k8s/ 00-namespace.yml 20-resource-quota.yml 20-limit-range.yml web/ deployment.yml service.yml worker/ deployment.yml ``` note: currently this would conflict with overlays

mortar gives random excon error when kubectl does not work

2

``` $ kubectl get pod Unable to connect to the server: x509: certificate signed by unknown authority ``` ``` $ mortar deploy asdf asdf ... ..gems/excon-0.62.0/lib/excon/ssl_socket.rb:118:in `connect_nonblock': SSL_connect returned=1 errno=0...

no shooting unless (some) variables are set

1. fire with mortar 2. delete namespace 3. fire with mortar again `` POST /api/v1/namespaces/hello-world/limitranges => HTTP 403 Forbidden: limitranges "hello" is forbidden: unable to create new content in namespace...

a pod with two http containers is massively long due to all readiness/liveness probes etc so maybe somehow (magic?) enable this: ``` deployment-web-container1.yml deployment-web-container2.yml ``` where first file would contain...

deployed with `deploy` folder yamls: ``` {"level":"info","ts":1558540864.9111614,"logger":"cmd","msg":"failed to initialize service object for metrics: replicasets.apps \"akrobateo-66cccb4bcb\" is forbidden: User \"system:serviceaccount:kube-system:akrobateo\" cannot get resource \"replicasets\" in API group \"apps\" in the namespace...