| I'm extremely frustrated. | |
| I worked on our helmfile POC about eight months ago. I got working for a subset of charts we use; roughly six out of about | |
| 40 charts. That POC took me about two weeks to get done. In my opinion, that was too long for six charts but I was pleased | |
| with the outcome at the time and I chalked up the time to having never worked with helmfile before. | |
| After the successful POC, I moved on and put the project on the back burner until we could get more time to develop it | |
| fully. So, now I'm circling back to this project. Trying to understand how I got helmfile to work for the POC is | |
| unintuitive, complicated, and not at all DRY even though I used the recommended ways to DRY out our helmfile project at the | |
| time with extensive help from the maintainer for which I was truly grateful and still am. However, it is my opinion that |
| #!/usr/bin/env bash | |
| # ——————————————————————————————————————————————————————— | |
| # BashMatic Utilities Library | |
| # ——————————————————————————————————————————————————————— | |
| # © 2017-2020 Konstantin Gredeskoul, All rights reserved. | |
| # | |
| # Distributed under the MIT LICENSE. | |
| # | |
| # Sources: https://github.com/kigster/bashmatic | |
| # ——————————————————————————————————————————————————————— |
| package mypackage | |
| import ( | |
| "net/http" | |
| "github.com/gobuffalo/buffalo" | |
| gateway "github.com/grpc-ecosystem/grpc-gateway/runtime" | |
| "github.com/pkg/errors" | |
| "github.com/prometheus/client_golang/api" | |
| "google.golang.org/grpc/status" |
| ### Keybase proof | |
| I hereby claim: | |
| * I am notjames on github. | |
| * I am cloaked1 (https://keybase.io/cloaked1) on keybase. | |
| * I have a public key ASAy857Ke67AuD4yqtd9c59fqHEvV2NfXJbzTx0u-PJQaQo | |
| To claim this, I am signing this object: |
| #include <string> | |
| using namespace std; | |
| const string data[] = { | |
| "A1,string1", | |
| "A2,string2", | |
| "A3,string3", | |
| "A4,string4", | |
| "A5,string5", | |
| "A6,string6", |
| #!/bin/bash | |
| # USAGE | |
| # kubescan.sh [kubeconfig.yaml] > state.yaml | |
| # Goal: | |
| # - Provide a quick way to dump the state of a cluster for analysis | |
| # - Simplify verification of live state of the cluster | |
| KUBECONFIG=${1:-$KUBECONFIG} |
| ###################### | |
| ### CONFIG CHANGES ### | |
| ###################### | |
| set -g mode-keys vi | |
| #set -g default-terminal "screen-256color" | |
| # set -g default-terminal "linux" | |
| # remap prefix from 'C-b' to 'C-a' | |
| unbind C-b |
| /* Exercise: Loops and Functions #43 */ | |
| package main | |
| import ( | |
| "fmt" | |
| "math" | |
| ) | |
| func Sqrt(x float64) float64 { | |
| z := float64(2.) |
1. The table below shows the formulas for triangular, pentagonal, and hexagonal numbers.
| ... | ... | ... |
|---|---|---|
| Triangular | Tn = n(n+1)/2 | 1, 3, 6, 10, 15, ... |
| Pentagonal | Pn = n(3n-1)/2 | 1, 5, 12, 22, 35, ... |
| Hexagonal | Hn = n(2n-1) | 1, 6, 15, 28, 45, ... |
The number T285 = P165 = H143 = 40755 is a triangular number, a pentagonal number, and a hexagonal number. Write code to find the next number like this.
