Setting up caching with packrat with the following command.
#Optional to set location of cache, may be useful if we want a global cache for shiny deployment? Can be saved in .Renviron, I think.
#Sys.setenv(R_PACKRAT_CACHE_DIR = "/home/willbowditch/R/packratcache")
packrat::set_opts(use.cache=TRUE)
| --- | |
| ################################################################################ | |
| ## K8S Default Backend for Nginx if no endpoint is available e.g. 404 servers | |
| ############################################################################### | |
| apiVersion: extensions/v1beta1 | |
| kind: Deployment | |
| metadata: | |
| name: nginx-default-backend | |
| namespace: kube-system | |
| labels: |
| certifi==2016.8.8 | |
| elasticsearch-curator==4.0.6 | |
| PyYAML==3.11 |
| --- | |
| version: v3 | |
| variant: openshift-enterprise | |
| variant_version: '3.1' | |
| # The deployment key specifies the hosts and roles fo rthe deployment | |
| # and configuration values that apply to the deployment as a whole | |
| deployment: | |
| ansible_config: /usr/share/atomic-openshift-utils/ansible.cfg | |
| ansible_log_path: /tmp/ansible.log |
In order to enable oidc authenticator in kube-apiserver,
we need to have TLS enabled between kubectl and kube-apiserver, as well as between kube-apiserver and OpenID Provider(dex-worker here)
For simplicity, we will use cfssl to create the bundles.
Checkout and build dex
| README.md | |
| scripts/bootstrap | |
| _shared/cloud-init-template.sh | |
| common_variables.tf.json | |
| modules/reporting_hadoop/gateway.tf.json | |
| modules/reporting_hadoop/main.tf.json | |
| modules/reporting_hadoop/manager.tf.json | |
| modules/reporting_hadoop/master.tf.json | |
| modules/reporting_hadoop/slaves.tf.json |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
