heckj

E0223 13:43:33.896364   44376 notify.go:54] Error getting json from minikube version url: Error getting minikube version url via http: Get https://storage.googleapis.com/minikube/releases.json: x509: certificate signed by unknown authority
Starting local Kubernetes cluster...
Downloading Minikube ISO
E0223 13:43:35.775606   44376 start.go:107] Error starting host: Error attempting to cache minikube ISO from URL: Error downloading Minikube ISO: failed to download: failed to download to temp file: download failed: 5 error(s) occurred:

* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v1.0.6.iso: x509: certificate signed by unknown authority
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v1.0.6.iso: x509: certificate signed by unknown authority
* Temporary download error: Get https://storage.googleapis.com/minikube/iso/minikube-v1.0.6.iso: x509: certificate signed by unknown authority
* Temporary download error: Get https://storage.googlea

heckj

digraph {
PackageDescription
PackageDescription4
libc
POSIX -> libc
Basic -> {libc POSIX}
Utility -> {POSIX Basic}
SourceControl -> {Basic Utility}
PackageModel -> {Basic PackageDescription PackageDescription4 Utility}
PackageLoading -> {Basic PackageDescription PackageDescription4 Utility PackageModel}

heckj

git log --graph --pretty=format:'commit: %C(bold red)%h%Creset %C(red)<%H>%Creset %C(bold magenta)%d %Creset%ndate: %C(bold yellow)%cd %Creset%C(yellow)%cr%Creset%nauthor: %C(bold blue)%an%Creset %C(blue)<%ae>%Creset%n%C(cyan)%s%n%Creset'

heckj

# Install Docker on Xenial 16.04.1 x64
# Ref https://docs.docker.com/engine/installation/linux/ubuntulinux/
# No interactive for now.
export DEBIAN_FRONTEND=noninteractive
# Update your APT package index.
sudo apt-get -y update
# Update package information, ensure that APT works with the https method, and that CA certificates are installed.
sudo apt-get -y install apt-transport-https ca-certificates
# Add the new GPG key.
sudo apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D

heckj

{
    "selfLink": "/api/v1/nodes",
    "resourceVersion": "98782",
    "Items": [
        {
            "name": "black",
            "selfLink": "/api/v1/nodes/black",
            "uid": "e5b9a266-95b8-11e7-9fc1-eca86bff6780",
            "resourceVersion": "98770",
            "creationTimestamp": "2017-09-09T23:45:01Z",

heckj

reporting-disabled = true
bind-address = "localhost:8088"

[meta]
  dir = "/data/meta"
  retention-autocreate = true
  logging-enabled = true

[data]
  dir = "/data/data"

heckj

  should be able to override the image's default commmand (docker entrypoint) [Conformance]
[It] should be able to override the image's default commmand (docker entrypoint) [Conformance]
  should be able to override the image's default commmand (docker entrypoint) [Conformance]
  should provide node allocatable (memory) as default memory limit if the limit is not set [Conformance] [sig-storage]
[It] should provide node allocatable (memory) as default memory limit if the limit is not set [Conformance] [sig-storage]
  should provide node allocatable (memory) as default memory limit if the limit is not set [Conformance] [sig-storage]
  should contain environment variables for services [Conformance]
[It] should contain environment variables for services [Conformance]
  should contain environment variables for services [Conformance]
  should provide container's memory limit [Conformance] [sig-storage]

heckj

Joe's SIG Docs review process

• Go through all the open PRs.
  • I generally start with the pull request index and just open tabs for each one, and knock them down tab-by-tab.

The general review process I use:

• make sure they’ve had something respond something to them, even if it’s just assigning yourself to come back to it. Especially for new names, or folks first PR (often indicated by an unsigned CLA) I try to thank them or otherwise interact positively.
  • if the CLA isn’t signed, make a comment referencing the author with @<name> to send a message back asking them to sign the CLA so we can accept the PR.

heckj

Summarizing the thinking of this "let's move to use Hugo" to make sure we're all on the same page/have shared understanding. Please call out what I've mistaken or misunderstood:

• localization within Jekyll had a number of significant pain points. Most of which revolved around the Jekyll plugin Polyglot (http://polyglot.untra.io). The key elements I've heard repeated were:

1. difficulty in sharing a consistent Ruby/Jekyll development setup
2. slow static-site render times for local developers doing the translations
3. we didn't want to maintain separate repositories for separate languages while doing the localization efforts (current CN translated content is being updated in https://github.com/kubernetes/kubernetes-docs-cn)

• we want to continue to leverage Netlify, with whom we have some agreement (or maybe just subscribe to their service) - but in general, we're happy with what we're getting there.
• implying that we didn't have a tremendous appetite to look at alternative solutions while also addressin

heckj

function force_sync {
  # $1 == dirname
  # assumes that your local fork is at origin, and there is a remote named 'upstream'
  # named "upstream" with the upstream sources
  # DOES NOT ASK QUESTIONS, WILL KILL LOCAL WORK
  if [ -d $1/.git ]; then
    cd $1
    git checkout master
    git reset --hard origin/master
    git fetch --all --prune