jedi4ever

Installation

• did brew install pulumi, installed 1.0.0 , running it keeps nagging about brew upgrade to 1.0.1
• I wonder if there is a phone-home option, then it needs an optional opt-out
• I'd expect pulumi init instead of new
• pulumi needs documentation on the bootstrap for the state bucket (correct permissions)
• pulumi login defaults to the saas platform, and says alternative logins available. not too clear , a select local would be nice
• also the path where is stores the files should be asked for during installation
• pulumi new --secrets-provider=passphrase (default I assume) has no way to initialize the secret from the CLI (like reading it from stdin or file)
• why is bin in .gitignore (because typescript compiles in ./bin)

MaxymVlasov

# How to install:
# pre-commit install --install-hooks && pre-commit install --install-hooks -t commit-msg

# How temporary skip one of hooks: https://pre-commit.com/#temporarily-disabling-hooks


repos:
#######
# ALL #
#######

jkatz

# Copyright 2019-2022 Jonathan S. Katz
# 
# MIT License
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:

lizthegrey

default['sshd']['sshd_config']['AuthenticationMethods'] = 'publickey,keyboard-interactive:pam'
default['sshd']['sshd_config']['ChallengeResponseAuthentication'] = 'yes'
default['sshd']['sshd_config']['PasswordAuthentication'] = 'no'

ameenkhan07

What to Expect and Tips

• 45-minute systems interview, focus on responding to real world problems with an unhealthy service, such as a web server or database. The interview will start off at a high level troubleshooting a likely scenario, dig deeper to find the cause and some possible solutions for it. The goal is to probe your knowledge of systems at scale and under load, so keep in mind the challenges of the Facebook environment.
• Focus on things such as tooling, memory management and unix process lifecycle.

Systems

More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell, memory etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).

Design/Architecture 

Interview is all about taking an ambiguous question of how you might build a system and letting

Mykolaichenko

  - job_name: "envoy-proxy-service"
    metrics_path: "/stats/prometheus"
    consul_sd_configs:
      - server: "localhost:8500"
        scheme: "http"
        services:
          - envoy-client
          - envoy-aws-server
          - envoy-sj-server

milesbxf

###################################################
##
## Alertmanager YAML configuration for routing.
##
## Will route alerts with a code_owner label to the slack-code-owners receiver 
## configured above, but will continue processing them to send to both a
## central Slack channel (slack-monitoring) and PagerDuty receivers
## (pd-warning and pd-critical)
##

tkuther

apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: filebeat
  namespace: kube-system
  labels:
    k8s-app: filebeat
spec:
  template:
    metadata:

ahume

Concourse on Kubernetes

This document outlines Brandwatch's Concourse installation running on Kubernetes. The full configuration can be found at https://github.com/BrandwatchLtd/concourse-ops (internal only currently). It's a fairly new installation (1-2 weeks) and we're slowly migrating work from our existing BOSH installation to this.

Comments/questions welcome below.

Summary

• Google GKE
• ConcourseCI (from stable/concourse chart)

ryboe

# use the latest ubuntu environment (18.04) available on travis
dist: bionic

language: go

# You don't need to test on very old versions of the Go compiler. It's the user's
# responsibility to keep their compiler up to date.
go:
  - 1.16.x