A presentation looking at Kubernetes cluster security. A good overview of the main issues, and some good advice for fixing the low hanging fruit issues.
https://docs.google.com/presentation/d/1XgopLXWjMdJojVFh_fPDJ2RllNpT9_y72vJSJ7oz57w/edit#slide=id.g5df3ccf4f3_0_103
https://docs.google.com/presentation/d/1XgopLXWjMdJojVFh_fPDJ2RllNpT9_y72vJSJ7oz57w/edit#slide=id.g5df3ccf4f3_0_103
Google Docs
Kubernetes Security Low-Hanging Fruit - CCAU 2019
Kubernetes Security Low-Hanging Fruit Container Camp #10 Sydney, July 2019 @lukeb0nd
Python_Security_Best_Practices_Cheat_Sheet__rev.pdf
67.1 KB
Python_Security_Best_Practices_Cheat_Sheet__rev.pdf
Kubernetes operator and CLI tool for encrypting Kubernetes secrets
https://github.com/amaizfinance/secreter
https://github.com/amaizfinance/secreter
GitHub
GitHub - nrvnrvn/secreter: ⛔️ DEPRECATED Kubernetes operator and CLI tool for encrypting and managing Kubernetes secrets
⛔️ DEPRECATED Kubernetes operator and CLI tool for encrypting and managing Kubernetes secrets - nrvnrvn/secreter
A useful library for anyone writing Go-based HTTP services. Sundheit allows you to register async health checks for your dependencies and the service itself and provides a health endpoint that exposes status and health metrics.
https://github.com/AppsFlyer/go-sundheit
https://github.com/AppsFlyer/go-sundheit
GitHub
GitHub - AppsFlyer/go-sundheit: A library built to provide support for defining service health for golang services. It allows you…
A library built to provide support for defining service health for golang services. It allows you to register async health checks for your dependencies and the service itself, provides a health end...
https://www.reddit.com/r/devops/comments/cowe8e/is_it_important_to_learn_itil_for_a_devops_role/?utm_medium=android_app&utm_source=share
Is it important to learn ITIL for a DevOps role?
From my perspective, the answer is: *Not important at all!*
As others have said, there is no reason to know ITIL to become a DevOps Engineer. ITIL and DevOps are diametrically opposed views of how to accomplish the same goal. The goal of "reduce risk" is the same, but the approach to achieve it is completely different.
Here are some comparisons of the ITIL Discipline vs DevOps Culture:
Pipeline:
* *ITIL*: The IT pipeline consists of large batches of accurately planned work transitioned between strategy, development, and operations
* *DevOps*: The DevOps pipeline consists of small batches that are continuously integrated, and iterated on, based on feedback from MVP experiments
Process:
* *ITIL*: Process solves your problems. ITIL v4 has 34 Practices that follow a prescribed process
* *DevOps*: Process is important, but being reactive to change and making decisions based on metrics is how you manage IT
Narrative:
* *ITIL*: The deep, repeated narrative is one of planning, control, and documentation
* *DevOps*: The deep, repeated narrative is one of culture, automation, trust, experimentation, and fast feedback loops
Risk:
* *ITIL*: Risk is mitigated through planning and documentation
* *DevOps*: Risk is mitigated through practice and repeatable automation
Culture:
* *ITIL*: It's all about following the process
* *DevOps*: It's all about speed, agility, and repeatability
To summarize:
ITIL is: aim, aim, aim, shoot.
DevOps is: aim, shoot, measure where it lands, adjust your aim, shoot again, repeat until you hit the target consistently. ;-)
\~jr
Is it important to learn ITIL for a DevOps role?
From my perspective, the answer is: *Not important at all!*
As others have said, there is no reason to know ITIL to become a DevOps Engineer. ITIL and DevOps are diametrically opposed views of how to accomplish the same goal. The goal of "reduce risk" is the same, but the approach to achieve it is completely different.
Here are some comparisons of the ITIL Discipline vs DevOps Culture:
Pipeline:
* *ITIL*: The IT pipeline consists of large batches of accurately planned work transitioned between strategy, development, and operations
* *DevOps*: The DevOps pipeline consists of small batches that are continuously integrated, and iterated on, based on feedback from MVP experiments
Process:
* *ITIL*: Process solves your problems. ITIL v4 has 34 Practices that follow a prescribed process
* *DevOps*: Process is important, but being reactive to change and making decisions based on metrics is how you manage IT
Narrative:
* *ITIL*: The deep, repeated narrative is one of planning, control, and documentation
* *DevOps*: The deep, repeated narrative is one of culture, automation, trust, experimentation, and fast feedback loops
Risk:
* *ITIL*: Risk is mitigated through planning and documentation
* *DevOps*: Risk is mitigated through practice and repeatable automation
Culture:
* *ITIL*: It's all about following the process
* *DevOps*: It's all about speed, agility, and repeatability
To summarize:
ITIL is: aim, aim, aim, shoot.
DevOps is: aim, shoot, measure where it lands, adjust your aim, shoot again, repeat until you hit the target consistently. ;-)
\~jr
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Curlie provides a CLI tool for making HTTP requests. It aims to offer the power of Curl but with an easier to use and more informative UI.
https://curlie.io/
https://curlie.io/
As the Kubernetes API becomes more commonplace, provisioning small Kubernetes clusters becomes more useful. K3up provides a simple point-and-shoot solution to install a single-node cluster over SSH.
https://sysadmins.co.za/provision-k3s-on-the-fly-with-k3sup/
https://github.com/alexellis/k3sup
https://sysadmins.co.za/provision-k3s-on-the-fly-with-k3sup/
https://github.com/alexellis/k3sup
Ruan
Provision k3s on the fly with k3sup
In this tutorial I will show you one awesome utility, called k3sup
[https://github.com/alexellis/k3sup] that allows you to provision k3s
[https://github.com/rancher/k3s] on any local or remote virtual machine,
whether the architecture is x86_64, arm, arm64…
[https://github.com/alexellis/k3sup] that allows you to provision k3s
[https://github.com/rancher/k3s] on any local or remote virtual machine,
whether the architecture is x86_64, arm, arm64…