cknowles

{
  "deviceId": "31cf54b7-1234-1234-1234-1234567890ab",
  "deviceType": 403,
  "modelName": "DHUM_056905_WW",
  "subModelNm": null,
  "sensorType": null,
  "alias": "Dehumidifier",
  "deviceCode": "AI02",
  "networkType": "02",
  "tftYn": "N",

cknowles

Keybase proof

I hereby claim:

• I am cknowles on github.
• I am cknowles (https://keybase.io/cknowles) on keybase.
• I have a public key ASD8SDPrvoGDbp3v6cHy4pfLm2JJwyeGUcmyF9rEdvptSAo

To claim this, I am signing this object:

cknowles

# Common settings.
global:
  proxy:
    # istio egress capture whitelist
    # https://istio.io/docs/tasks/traffic-management/egress.html#calling-external-services-directly
    # example: includeIPRanges: "172.30.0.0/16,172.20.0.0/16"
    # would only capture egress traffic on those two IP Ranges, all other outbound traffic would
    # be allowed by the sidecar
    # TODO configure native Istio ServiceEntry and get rid of this - https://istio.io/docs/tasks/traffic-management/egress/#configuring-istio-external-services
    includeIPRanges: "10.2.0.0/16,10.3.0.0/16" # pod and service CIDR for our kube-aws clusters

cknowles

clusterName: k8s-dev-v8
releaseChannel: stable
sshAccessAllowedSourceCIDRs: []
adminAPIEndpointName: versioned
apiEndpoints:
    - name: versioned
    dnsName: kubeapi-dev-v8.OBFUSCATED
    loadBalancer:
      createRecordSet: true
      hostedZone:

cknowles

Introduction

A draft design for kube-aws plugins. Plugins are initially defined as additions to a kube-aws generated cluster that are not part of the core feature set of providing an easy to use, highly available, best practice cluster on AWS. Plugins can also later be used for built-in functionality to provide a more modular deployment and ability to test.

Initial Use Cases

1. A user wishes to deploy a component by default to their cluster instances outside of Kubernetes, e.g. a monitoring agent.

cknowles

'use strict';

const AWS = require('aws-sdk');
const https = require('https');

const config = {
};
const projectLookupCache = {
};