Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
| name: "Full Job Example" | |
| on: | |
| workflow_dispatch: | |
| inputs: | |
| version: | |
| description: Version (See Releases) | |
| required: true | |
| jobs: |
| { | |
| local this = self, | |
| local clusterWideKinds = [ | |
| 'APIService', | |
| 'CertificateSigningRequest', | |
| 'ClusterRole', | |
| 'ClusterRoleBinding', | |
| 'ComponentStatus', | |
| 'CSIDriver', |
| apiVersion: apps/v1 | |
| kind: Deployment | |
| metadata: | |
| name: istio-ingressgateway | |
| spec: | |
| template: | |
| spec: | |
| containers: | |
| - name: istio-proxy | |
| readinessProbe: |
| #!/bin/bash | |
| # Install k3d | |
| k3d --version || wget -q -O - https://raw.githubusercontent.com/rancher/k3d/master/install.sh | bash | |
| # verify it | |
| k3d check-tools | |
| # create a volume and cluster | |
| docker volume create kube-volume |
| package main | |
| import ( | |
| "os" | |
| "os/signal" | |
| "syscall" | |
| "fmt" | |
| "time" | |
| "net/http" | |
| ) | |
| func main() { |
| - What do Etcd, Consul, and Zookeeper do? | |
| - Service Registration: | |
| - Host, port number, and sometimes authentication credentials, protocols, versions | |
| numbers, and/or environment details. | |
| - Service Discovery: | |
| - Ability for client application to query the central registry to learn of service location. | |
| - Consistent and durable general-purpose K/V store across distributed system. | |
| - Some solutions support this better than others. | |
| - Based on Paxos or some derivative (i.e. Raft) algorithm to quickly converge to a consistent state. | |
| - Centralized locking can be based on this K/V store. |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
| ! -------------------------------------------------------------------------------- | |
| ! This example configuration shows what WE did to get Amazon VPC working with our | |
| ! ASAs. We use version 8.3(1). This config has not been reviewed or otherwise | |
| ! blessed in any way by anyone at Amazon. YMMV. | |
| ! | |
| ! It differs from Amazon's supplied config by using two different sets of | |
| ! crypto maps and ACLs, so it brings both tunnels up simultaneously. | |
| ! | |
| ! For the purposes of the example, the physical datacenter network is 172.16.1.0/24 | |
| ! and the VPC is 10.0.0.0/16. |
| #!/usr/bin/env ruby | |
| require 'rubygems' | |
| require 'rest-client' | |
| require 'json' | |
| client = RestClient::Resource.new('http://0.0.0.0:3000', | |
| :user => 'admin', | |
| :password => 'changeme', | |
| :headers => { :accept => :json }) |
| class Array | |
| def expand_ranges | |
| self.collect { |wtf| wtf.is_a?(Range) ? wtf.to_a : wtf }.flatten | |
| end | |
| end | |
| [1..15, 19, 21..25].expand_ranges.each { |i| puts i } |