I hereby claim:
- I am mariusv on github.
- I am mariusv (https://keybase.io/mariusv) on keybase.
- I have a public key ASCqaSPOQVTDf0CrWWWHfGsE_nSVHBdJJ5pQpxPmuEtmcwo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
source 'http://rubygems.org' | |
gem 'meinside-ruby', github: 'meinside/meinside-ruby' # my ruby scripts and libraries | |
gem 'thor' | |
gem 'geocoder' |
--- | |
- hosts: all | |
sudo: yes | |
tasks: | |
- name: Enable EPEL | |
command: yum-config-manager --enable epel | |
- name: Install remi repo. |
--- | |
- hosts: all | |
sudo: yes | |
tasks: | |
- name: Install EPEL repo. | |
yum: | |
name: https://dl.fedoraproject.org/pub/epel/epel-release-latest-{{ ansible_distribution_major_version }}.noarch.rpm | |
state: present |
# Sends events to Flapjack for notification routing. See http://flapjack.io/ | |
# | |
# This extension requires Flapjack >= 0.8.7 and Sensu >= 0.13.1 | |
# | |
# In order for Flapjack to keep its entities up to date, it is necssary to set | |
# metric to "true" for each check that is using the flapjack handler extension. | |
# | |
# Here is an example of what the Sensu configuration for flapjack should | |
# look like, assuming your Flapjack's redis service is running on the | |
# same machine as the Sensu server: |
const request = require('request'); | |
module.exports = function(context, callback) { | |
var url = 'https://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20yahoo.finance.quotes%20where%20symbol%20in%20(%22rax%22)%0A%09%09&format=json&diagnostics=true&env=http%3A%2F%2Fdatatables.org%2Falltables.env&callback='; | |
var aux = {}; | |
request(url, function (error, response, body) { | |
if (!error && response.statusCode == 200) { | |
var info = JSON.parse(body); |
Delete all containers
$ docker ps -q -a | xargs docker rm
-q prints only the container IDs -a prints all containers
Notice that it uses xargs to issue a remove container command for each container ID
DevOps started out as "Agile Systems Administration". In 2008, Andrew Shafer did a talk called "Agile Infrastucture" addressing issues around involving more of the company in the same disciplines as programmers.
In 2009, Patrick Debois created "DevOpsDays" conference to help to bring it to light. However, it wouldn't begin to trend until about 2010, when people would begin to describe it as a standalone discipline.
Today, DevOps goes beyond just developers, systems administration and infrastructure, its about [dev, ops, agile, cloud, open source and business](https://blogs.the451group.com/opensource/2010/03/03/devops-mixing-dev-ops-agile-cloud-open-source-and-busi
Steps for the workaround: | |
Check the yaml of current deployment for the dns-controller. Here you will find the path to the --watch-ingress setting. | |
`kubectl get deployment -n kube-system dns-controller -o yaml` | |
Use the path and make a patch of the deployment. I think the path here will work for most. | |
```kubectl patch deployment -n kube-system dns-controller --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/command/1", "value":"--watch-ingress=true"}]'``` |