Skip to content

Instantly share code, notes, and snippets.

package main
import (
"crypto/sha256"
"crypto/tls"
"encoding/json"
"flag"
"fmt"
"io/ioutil"
"net/http"
@duglin
duglin / params.yaml
Last active July 27, 2017 05:13
params.yaml
spec:
serviceClassName: user-provided-service
planName: default
parameters:
- name: username # easy name/value pair case
value: root
- name: password # pull value from a secret's key
valueFrom:
secretKeyRef:
name: mySecret1
@duglin
duglin / PodPreset Ramblings
Last active July 12, 2017 20:46
PodPreset Ramblings
Some aspects that influence my thinking on this:
- having PodPresets in a Binding is causing problems
- first, because we'll be constantly chasing the real PodPreset definition
- second, because we actually don't want a full PodPreset with all of its features,
we just need the bits related to Secrets
- third, PodPresets (as of now) are immutable
- we need to allow for people to specify more than one LabelSelector at a time to support
upgrading of apps
- as long as the LabelSelector is immutable and embedded in a Binding we should separate the
idea of asking for creds from linking the creds to an app to allow for changing LabelSelectors
{
"_id": "apsMyserviceParametersDemo_id",
"catalog": {
"bindable": true,
"name": "apsMyserviceParametersDemo",
"tags": [
"big_data",
"ibm_created"
],
"version": "",

word

two words

with-dashes

with'punct

with ' punct

with . dot

with ... dots

apiVersion: v1
kind: PersistentVolume
metadata:
name: local-volume-test
labels:
type: local
spec:
capacity:
storage: 5Gi
accessModes:

Table of Contents

line link

section 1

section

Section

section 1

section 1

all: init build test lint
.PHONY: format coverage
# If DOCKER is defined then make it the full docker cmd line we want to use
ifneq ($(origin DOCKER),undefined)
DOCKER=docker run --rm -ti \
-v $(PWD):/go/src/github.com/kubernetes-incubator/service-catalog \
scbuildimage
endif
package main
import (
"bytes"
"encoding/json"
"flag"
"fmt"
"io"
"net"
"os"
package main
/*
fakepod:
This program will monitor all of the containers running on a node and for each
one will check to see if its a Kubernetes managed one. If so, then it skips it.
If it's not managed by Kubernetes then we want to calculate the total amount
of resources used by all of these containers and create a pod which reserves