(gist: https://gist.github.com/ded15819fd881acd3133b2f9c5c3b795)
Test Mod
- Plan: "Scan the Space: Go Wide then Go Deep"
| Terraform: Using JSON with JQ to filter and extract output values | |
| ================================================================= | |
| - Sometimes we need clean, elegant extraction of values from the terraform output to pass data to a next stage pipeline. | |
| - JSON and JQ make this reliable, simple and fun! | |
| ``` | |
| gmonkey@tfvm:~/Ship/5ncn$ terraform output -json cluster_slave_private_addresses| jq .value | |
| [ | |
| "192.168.101.6", |
| FROM openshift/origin | |
| MAINTAINER SRE Team <sre@local> | |
| ENV HOME=/home/jenkins | |
| USER root | |
| # Install headless Java | |
| RUN yum install -y centos-release-scl-rh && \ | |
| x86_EXTRA_RPMS=$(if [ "$(uname -m)" == "x86_64" ]; then echo -n java-1.8.0-openjdk-headless.i686 ; fi) && \ |
| Quick Notes on installation Options for Ubuntu | |
| ============================================== | |
| 1. Directly on Ubuntu | |
| (Note: This one is entangled with the Oracle licensing nonsense. Lately they've threatened to stop free downloads of Java, so Caveat Emptor) | |
| ``` |
| Book Summary notes: Implementing Azure Cloud Design Patterns | |
| ============================================================ | |
| - Commentary | |
| - Summary | |
| - Errata notes | |
| Chapter 1: | |
| ========== |
| Review of possible options for deploying Hashicorp Vault | |
| ======================================================== | |
| 1. VM based | |
| 2. Containerised | |
| 3. AWS | |
| 4. Azure | |
| 5. DC/OS | |
| 6. Kubernetes |
| (The following call is repeated over > 15 mins) | |
| ``` | |
| 2019-01-24T18:33:18.472Z [DEBUG] plugin.terraform-provider-azurerm_v1.21.0_x4: 2019/01/24 18:33:18 [TRACE] Waiting 30s before next try | |
| module.securitycenter.azurerm_security_center_workspace.sc: Still modifying... (ID: redacted3, 14m40s elapsed) | |
| module.securitycenter.azurerm_security_center_workspace.sc: Still modifying... (ID: redacted3, 14m50s elapsed) | |
| module.securitycenter.azurerm_security_center_workspace.sc: Still modifying... (ID: redacted3, 15m0s elapsed) | |
| 2019-01-24T18:33:48.472Z [DEBUG] plugin.terraform-provider-azurerm_v1.21.0_x4: 2019/01/24 18:33:48 [DEBUG] AzureRM Request: | |
| 2019-01-24T18:33:48.472Z [DEBUG] plugin.terraform-provider-azurerm_v1.21.0_x4: GET /subscriptions/redacted/providers/Microsoft.Security/workspaceSettings/default?api-version=2017-08-01-preview HTTP/1.1 | |
| 2019-01-24T18:33:48.472Z [DEBUG] plugin.terraform-provider-azurerm_v1.21.0_x4: Host: management.azure.com |
(gist: https://gist.github.com/ded15819fd881acd3133b2f9c5c3b795)
Test Mod
Most of the catastrophes on I.T systems occur because of human error. Put succinctly "If it aint broke don't fix it". Here is a list of questions you can process every change you want to make on a given system through before you make that change. It was gathered from years of painful experience and, if followed will keep you on the right side of a performance review if your job is to keep critical, complex systems running (especially ones you've inherited and are not yet completely familiar with). The faster you get at accurately answering these questions in response to every requirement for a systems change, the better.
| apiVersion: v1 | |
| items: | |
| - apiVersion: v1 | |
| kind: Pod | |
| metadata: | |
| creationTimestamp: "2019-11-15T07:55:25Z" | |
| generateName: kube-state-metrics-549767c89b- | |
| labels: | |
| app: kube-state-metrics | |
| pod-template-hash: 549767c89b |