These variables will be used for this snippet. Please substitute accordingly.
export RootCAName="root_ca"
export InterCAName="inter_ca"
export CommonName="hashidemos.io"
export InterCommonName="inter.hashidemos.io"
export Root_CA_ttl="730h"
export Inter_CA_ttl="350h"
export Cert_ttl="8h"
| ### Configure variables | |
| These variables will be used for this snippet. Please substitute accordingly. | |
| ```bash | |
| export RootCAName="root_ca" | |
| export InterCAName="inter_ca" | |
| export CommonName="hashidemos.io" | |
| export InterCommonName="inter.hashidemos.io" | |
| export Root_CA_ttl="730h" | |
| export Inter_CA_ttl="350h" | |
| export Cert_ttl="8h" |
| import * as pulumi from "@pulumi/pulumi"; | |
| import * as k8s from "@pulumi/kubernetes"; | |
| import * as k8sOutput from "@pulumi/kubernetes/types/output"; | |
| import * as k8sapi from 'kubernetes-client'; | |
| const job = new k8s.batch.v1.Job("job", { | |
| spec: { | |
| template: { | |
| spec: { | |
| containers: [{ |
| package main | |
| import ( | |
| "context" | |
| "flag" | |
| "fmt" | |
| "log" | |
| "net/http" | |
| "os" | |
| "os/signal" |
Our goal is to save sensitive data in a MySQL database in a responsible way, and be able to read/write it programmatically in a PHP web application. Asymmetric encryption would be best, but is not practical here. Symmetric encryption with a strong algorithm and hard-to-guess cipher is acceptable, but not if we store the cipher in plain text on the same server where the database credentials also live in plain text!
This work-in-progress is subject to change if/when I come up with a better scheme, but for now, the plan is to:
| image: docker.mydomain.com/build/kube-go-make | |
| variables: | |
| DOCKER_TAG: docker.mydomain.com/myapp/home:$CI_COMMIT_REF_SLUG | |
| DOCKER_HOST: tcp://localhost:2375 | |
| DOCKER_DRIVER: overlay | |
| PROD_RSYNC_HOST: myprodserver.com | |
| DOMAIN: mydomain.com | |
| CHART_DIR: chart |
This list has moved to a GitHub repo for easier tracking: https://github.com/coreos/awesome-kubernetes-extensions
Please comment below if you are using Kubernetes Third-Party Resources and I will add you to the list.
Known Users:
| #!/boot/bzImage | |
| # Linux kernel userspace initialization code, translated to bash | |
| # (Minus floppy disk handling, because seriously, it's 2017.) | |
| # Not 100% accurate, but gives you a good idea of how kernel init works | |
| # GPLv2, Copyright 2017 Hector Martin <marcan@marcan.st> | |
| # Based on Linux 4.10-rc2. | |
| # Note: pretend chroot is a builtin and affects the current process | |
| # Note: kernel actually uses major/minor device numbers instead of device name |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".
