joshgav

Appendix: Contributors

Thank you to the many members of CNCF WG Platforms who have contributed feedback and insights on this paper, in particular the following:

• Abby Bangser
• Abhinav Mishra
• Abi Noda
• Alex Chesser
• Brad Bazemore

joshgav

• https://github.com/kidd/org-gcal.el
• https://github.com/shiraily/gcal-sync
• https://github.com/eviallet/Tasks
• https://github.com/Davepar/gcalendarsync
• https://github.com/ahayworth/gcal-sync
• https://github.com/amancevice/terraform-aws-facebook-gcal-sync
• https://github.com/bergercookie/taskwarrior-syncall

joshgav

Clusters for all cloud tenants

A decision which faces many large organizations as they adopt cloud architecture is how to provide isolated spaces within the same environments and clusters for various teams and purposes. For example, marketing and sales applications may need to be isolated from an organization's customer-facing applications; and development teams building any app usually require extra spaces for tests and verification.

Namespace as unit of tenancy

To address this need, many organizations have started to use namespaces as units of isolation and tenancy, a pattern previously described by Google and Kubernetes contributors. But namespace-scoped isolation is often insufficient because some concerns are managed at cluster scope. In particular, installing new resource types (CRDs) is a cluster-scoped activity; and today independent te

joshgav

# envsubst invokes all shell substitutions in a file
# use by first sourcing this file, e.g. `source envsubst.sh` or `. envsubst.sh`, 
#   and then invoking `envsubst` on STDIN or a specific file
# it should only be invoked on trusted or scrubbed files to avoid injection attacks
function envsubst {
  local infile=${1}

  if [[ "${SUPPRESS_ENVSUBST_WARNING}" != "1" ]]; then
    >&2 echo "[WARNING] the envsubst function should only be used on trusted files because it is vulnerable to injection attacks"
  fi

joshgav

# install tmux
TMUX_VER=2.9a
LIBEVENT_VER=2.1.10
PREFIX=${HOME}/.local

# get tmux and libevent
curl -LO https://github.com/tmux/tmux/releases/download/${TMUX_VER}/${TMUX_VER}.tar.gz
curl -LO https://github.com/libevent/libevent/releases/download/release-${LIBEVENT_VER}-stable/libevent-${LIBEVENT_VER}-stable.tar.gz

tar -xzf "./tmux-${TMUX_VER}.tar.gz"

joshgav

Open source on GitHub: what and why

• Participants: users, contributors and maintainers.
  • We're looking for users.
  • README.md and CONTRIBUTING.md
• Why open source?
  • Collect better feedback on our software from users.
  • Gather direct insights into how users use our software.
  • Developers are empowered to:
    1. fix problems and answer questions themselves and maybe even blog about it

1. open detailed and actionable issues for us

joshgav

#! /usr/bin/env bash
# requires cifs-utils - `apt install cifs-utils`

group_name=joshgav-oryx-test-group
group_location=westus2

storage_account_name=joshgavoryxsharetest
storage_account_group_name=${group_name}
storage_account_location=${group_location}
share_name=intermediate

joshgav

app_name=your-unique-name
app_repo_url=https://github.com/your-name-here/your-repo-here
location=westus
# choose from: `az webapp list-runtimes --linux`
runtime='NODE|10.10'
env_vars=(
    APPINSIGHTS_INSTRUMENTATIONKEY=af4b1113-bc85-41d0-be2b-343c3f178b7b
    YOUR_ENV_VAR=test
)

joshgav

declare prefix="azuregosdkjuglaptop"

# cleanup_groups requests deletion of groups with names starting with `prefix`
# it returns after request acceptance, i.e. it does not wait for deletion to actually finish
# `prefix` string "___": first letters of names of groups to delete
function cleanup_groups () {
    declare prefix=${1:-"___"} # default to unlikely value for safety

    # set up jmespath query
    jmespath_query="[? starts_with(name, \`${prefix}\`)].name"

joshgav

• ACR: https://docs.microsoft.com/en-us/rest/api/containerregistry/registries/checknameavailability
• Analysis: https://docs.microsoft.com/en-us/rest/api/analysisservices/servers/checknameavailability
• CDN: https://docs.microsoft.com/en-us/rest/api/cdn/checknameavailability/checknameavailability
• CosmosDB: https://docs.microsoft.com/en-us/rest/api/documentdbresourceprovider/databaseaccounts/checknameexists
• Event Hubs: https://docs.microsoft.com/en-us/rest/api/eventhub/namespaces/checknameavailability
• IoT Hubs: https://docs.microsoft.com/en-us/rest/api/iothub/iothubresource/checknameavailability
• Key Vault: https://docs.microsoft.com/en-us/rest/api/keyvault/vaults/checknameavailability
• Media: https://docs.microsoft.com/en-us/rest/api/media/mediaservice/checknameavailability
• MySQL: https://docs.microsoft.com/en-us/rest/api/mysql/checknameavailability/execute
• Notification Hubs: https://docs.microsoft.com/en-us/rest/api/notificationhubs/namespaces/checkavailability