I hereby claim:
- I am cryptophobia on github.
- I am cryptophobia (https://keybase.io/cryptophobia) on keybase.
- I have a public key ASDF-iAOoXwdUk1mR-OKK9CHoOGW-OTBZPZPrM9n7NDWKAo
To claim this, I am signing this object:
#!/usr/bin/env sh | |
# Invoking this script: | |
# | |
# To install the latest stable version: | |
# curl https://deis.io/deis-cli/install-v2.sh | sh | |
# | |
# To install a specific released version ($VERSION): | |
# curl https://deis.io/deis-cli/install-v2.sh | sh -s $VERSION | |
# |
kubectl edit deploy deis-router -n deis | |
... | |
readinessProbe: | |
failureThreshold: 3 | |
httpGet: | |
path: /healthz | |
port: 9090 | |
scheme: HTTP | |
initialDelaySeconds: 1 |
From issue: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/699 | |
I've investigated using password encryption with weave. If you've followed the instructions for deploying kubernetes with KOps, the default deployment uses weave. Weave has a capability of employing password encryption. Once activated. The encryption in transit is seamless. | |
Here are the steps so far | |
Install Kubernetes with KOps per the z2jh documentation steps. | |
(optional) run kubectl --namespace kube-system get pods and verify there are weave-net pods | |
Create a password file. I did openssl rand -hex 128 >weave-passwd | |
Create a Kubernetes Secret in the kube-system namespace |
I hereby claim:
To claim this, I am signing this object:
Team Hephy Code of Conduct | |
Like the technical community as a whole, the Hephy team and community is made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the mission - including mentorship, teaching, and connecting people. | |
Diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to. This code applies equally to founders, mentors and those seeking help and guidance. | |
This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the technical communities in which we participate. | |
This code of conduct applies to all spaces managed by the Hephy project. This includes IRC, the mailing lists, the issue tracker, events, and any other forums created by the project team which the community uses for communication. In addition, violations of this code outs |