Skip to content

Instantly share code, notes, and snippets.

View moosh3's full-sized avatar
๐Ÿ
doing devop things

Alec Cunningham moosh3

๐Ÿ
doing devop things
View GitHub Profile
apiVersion: cert-manager.io/v1alpha2
kind: Issuer
metadata:
name: letsencrypt-staging
spec:
acme:
# The ACME server URL
server: https://acme-staging-v02.api.letsencrypt.org/directory
# Email address used for ACME registration
email: Hosting.DevOps@americanwell.com
apiVersion: helm.fluxcd.io/v1
kind: HelmRelease
metadata:
name: $RELEASE
namespace: default
spec:
chart:
git: git@github.com:fluxcd/flux-get-started
ref: master
path: charts/ghost
- etcd
- load balancing
- availability
- auto-scaling
- networking
- roll-back on faulty deployments
- persistent storage
- upgrading nodes
- removing nodes
- adding nodes
---
AWSTemplateFormatVersion: '2010-09-09'
Description: This Template creates an Amazon SNS topic that can send messages to two
Amazon SQS queues with appropriate permissions for one IAM user to publish to the
topic and another to read messages from the queues. MySNSTopic is set up to publish
to two subscribed endpoints, which are two Amazon SQS queues (MyQueue1 and MyQueue2).
MyPublishUser is an IAM user that can publish to MySNSTopic using the Publish API.
MyTopicPolicy assigns that permission to MyPublishUser. MyQueueUser is an IAM user
that can read messages from the two Amazon SQS queues. MyQueuePolicy assigns those
permissions to MyQueueUser. It also assigns permission for MySNSTopic to publish
AWSTemplateFormatVersion: 2010-09-09
Description: >-
Account Baseline IAM Groups, Roles and Managed Policies.
**WARNING** You will be billed for the AWS resources created if you create a
stack from this template.
Copyright 2018 Amazon.com, Inc. or its affiliates. All Rights Reserved.
Licensed under the Apache License, Version 2.0 (the "License").
You may not use this file except in compliance with the License.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-eks-nodegroup.html
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: developer-cluster-role
rules:
- apiGroups:
- ""
resources:
- "*"
verbs:
apiVersion: v1
kind: Service
metadata:
name: hello-kubernetes
spec:
type: NodePort
ports:
- port: 80
targetPort: 8080
selector:
apiVersion: v1
kind: Service
metadata:
name: hello-kubernetes
spec:
type: LoadBalancer
ports:
- port: 80
targetPort: 8080
selector:
[alec@613884-staging1 ~]$ curl -f localhost:9394/metrics
# HELP ruby_collector_working Is the master process collector able to collect metrics
# TYPE ruby_collector_working gauge
ruby_collector_working 1
# HELP ruby_collector_rss total memory used by collector process
# TYPE ruby_collector_rss gauge
ruby_collector_rss 20570112