How to prepare for Kubernetes certification (CKA)?

I am learning k8s and have no real-world experience with it outside my homelab. I'd like to get certified with CKA. I'm currently halfway through Mumshad Mannambeth's CKA course with some nice labs in Kodekloud, but I'm wondering if that's enough? What else would you recommend? thanks!

https://redd.it/k7351v
@r_devops

What is Everyone Using Instead of Puppet Pipelines

We've been using Puppet Pipelines extensively in my company. Our application is hosted on a mix of Windows/Linux VMs in a co-located DC. We use Pipelines to do run through all the steps, adjust the load balancer, turn off services, sync files from artifactory, turn it all back on, etc.

When they announced it was going away we started looking at other tools, but many seem dedicated to the cloud, AWS, hyper-converged VM stuff, etc. Has anyone else found a replacement? It's interesting that Puppet didn't even attempt to recommend what customers try to migrate to.

https://redd.it/k7ly9s
@r_devops

Come join our Kubernetes focused discord server!

I'm posting this again as I've made some changes to the server. Discord offers a lot of things the Slack workspace doesn't such as:

• A channel just for Kubernetes memes.
• Voice chats you can cry about production issues in
• Less professional so we can take out our frustrations on each other!
• Music rooms
• Doesn't do that annoying aesthetic shit with hyperlinks

https://discord.gg/zSSRFB3G3h

https://redd.it/k6zt1u
@r_devops

K8s volumes

https://medium.com/swlh/k8s-volumes-claims-part1-138012b6f52

https://redd.it/k7p0vk
@r_devops

What is the difference between services like mailgun and some backend script running on dedicated IP?

I am going to handle a newsletter for system with around 15k users and I am wondering whenever go for solutions like mailgun, or use something selfhosted.

I don't know what are some decent hardware / environment requirements for it.

https://redd.it/k7u5lt
@r_devops

Retrieva data from Azure App Configuration with Powershell

Hi yall,

I was suprised that MSFT still hasn't made a PowerShell Module to work with App Configuration data, so I made my own: [link](https://github.com/mieel/PSAzureAppConfiguration)

It uses the `az appconfig` in the background (so you need `azure cli` installed), but it added support for referencing to other keys, within the value.

## Install module

`install-module PSAzureAppConfiguration -Repository PSGallery`

## Usage

Log in Azure account using a service principal

`$clientId = 'client/app id'`

`$tenantId = 'tenant id'`

`$secret = 'client secret'`

`az login --service-principal --username $clientId --password $secret --tenant $tenantId`

Get configuration:

`$MyConfig = Get-AppConfigurationKeyValue -Store MyAppConfigStore -Label Production`

https://redd.it/k7txnd
@r_devops

Connecting to a vm using ssh with a NAT adapter

I heard bridged adapter was ok, but you couldn't access to the Internet using a bridged adapter. Is that true? I was able to ssh into my virtual box, and install linux packages, so I am not sure how that can be true. Anyway, how do you connect to a VM using a NAT adapter instead?

https://redd.it/k8780k
@r_devops

AWS MacOS EC2 machines vs Azure pipelines/GHA

The price per hour of mac EC2 machines are sitting at a little over 1 USD. I'm just wondering why their solution is better for CI/CD builds when Azure and GitHub already have pretty cheap alternatives that have worked for me in the past.

There seems to be a lot of hype over it and people calling it a game-changer. I just don't see what's special with their solution.

https://redd.it/k886p4
@r_devops

How to Configure OpenShift 4 Cluster Nodes: MachineConfig Operator and CoreOS

OpenShift and OKD 4 are using CoreOS for cluster nodes. The only way to configure them is to use Ignition and OSTree. Both of them are automated with MachineConfig Operator, which we will see in this video - how it works and how to use it to customize the cluster:

[https://www.youtube.com/watch?v=ntP4DVjrRd8&feature=youtu.be](https://www.youtube.com/watch?v=ntP4DVjrRd8&feature=youtu.be)

https://redd.it/k8eisq
@r_devops

Istio Service Mesh: A Beginners Guide

This post will give a high-level introduction to Istio and its related concepts and terminologies.
[https://www.loginradius.com/blog/async/istio-service-mesh/](https://www.loginradius.com/blog/async/istio-service-mesh/)

https://redd.it/k8fubi
@r_devops

Noob questions, what do you guys do when you experience an outage?

Hey guys,

I saw there were a couple of big outages this year and in the years before. What do you guys do when you experience such outages and is it total chaos like I imagine it in my head?

https://redd.it/k8ie2t
@r_devops

Have you guys notices any difference in mentality between those who come into devops from the dev side and those who come in from the ops side?

I've been thinking about this as I've been only recently getting into the devops field. My background is mainly ops. I came into this from systems engineering. I always saw development as something only really smart people do and I could never do that. But as I have been educating myself and interacting with developers, I found that I really loved the process of development. As I started writing up YAML files or Python scripts, I recognized that I was developing but never fully recognized it as that. I'm also starting to see how many ops people who do not understand development are frankly either really bad at their jobs or are becoming more and more specialized to the point of being boxed in. I never wanted to be like that and so it seemed like devops became the natural progression for me as an ops person. But I also think this came with being more exposed to devs and seeing how efficient many processes can become by incorporating more development (or automation) into my job.


How did you get into devops and what attracts you to it from either side?

https://redd.it/k8jn52
@r_devops

Moving from an Nginx VM with root access to a GH action deployed VM

Hello there

I have a legacy Nginx app which is the HTTP reverse service of our internal apps, running on a VM.And in the company, all the employees have root access to this VM and people edit in production files and restart nginx service by themselves.

It's defo not the best option or the best practice, but we are a small team and I would like to improve the process, make it more secure and scalable for a bigger team in the future.

At first I thought about having a repositories with only the \`/etc/nginx/\` folder that would be editable by the maintainer. Then, on push on master it would then try on a \`staging VM\` to deploy and runs \`nginx -t\` to test the config files. It would probably have a really fast deployment but it won't help for a from-scratch deployment with a completely brand new Debian, for example.

So my second thought went to an ansible playbook that will run the installation and file copying and run the test, but at the moment I am wondering then how I will run my test? Should my playbook first try to deploy on my \`staging VM\` and if everything is alright then deploy on my \`production VM\`

If I'm using a staging VM, then I guess I somehow need to reset this VM after use?

Or am I totally wrong and if so if you have any other idea please hit me up :)

I'm really keen to hear from you. Thank you in advance

https://redd.it/k8hthb
@r_devops

Is CodeArtifact feature full enough to replace Artifactory?

Have gotten a few different answers on this, but we’re a mid sized org and find Artifactory to be good, but expensive for what it is. We’ve been looking into CodeArtifact but wonder about limitations. What’s the consensus?

[View Poll](https://www.reddit.com/poll/k84oz5)

https://redd.it/k84oz5
@r_devops

Criteria for selecting an API gateway for a cloud environment

Hello everyone,

I am currently writing my thesis and would be very grateful for your opinions and comments.

Specifically, I'm dealing with how an API gateway can be used to secure an corporate network.

One part deals with the selection of an API gateway for a defined use case, here also with a focus on security features. I would be interested in concrete insights into the selection process in companies, how they select a API gateway and if the criteria mentioned below apply or if a certain aspect is missing.

In the following you will find a list between functional and non-functional properties:

# Functional features

**General features**

*Info: This includes general features of the product.*

* Analytics (Reports, Insides in the usage of the API)
* API technology (GraphQL, REST,.. )
* Caching
* Data security
* Error handling
* Life-Cycle Management (The ability to support different channels such as beta, test and production. This includes the ability to support multiple versions - API versioning.)
* Extensibility
* Import/Export API-definition
* Performance
* Load Balancing
* Management-API (An own API which is provided by the gateway itself for administration. For example to define new routes to services.)
* Monitoring
* Operation Model
* Payload transformation
* Logging
* Quote (Number of maximum connections per hour or other defined interval)
* Rate Limiting (Limitation of requests in a certain time interval. E.g. when providing a certain service, the customer can make 1000 requests / per hour)
* Scalability (This refers to the general ability that the product can scale depending on a certain performance)
* Redundancy (over different regions, but also redundancy in one region)

**Security features**

*Info: This includes security specific features of the product.*

* Audits (ISO 27001,9001; HIPAA; BSI C5)
* Authentication
* Authorization
* Security policies
* Thread protection
* Protocol (HTTP/HTTPS)
* Open/Closed source (the code can be viewed and checked)

# Non-functional features

**Support**

*Info: Aspects that can support the user during use.*

* Community (Developer forums, Meets-Ups,..)
* Documentation Software
* Support (commercial assistance with specific problems)
* Training (how to use the software)

**Operation**

*Info: Special aspects that can be considered when operating the product.*

* Configuration
* Usability
* Installation
* Maintenance intensity

**Producer**

*Info: This is about some aspects that concern the manufacturer and especially how the market share is.*

* Producer/Provider Eco-System
* Experience of the producer
* Size of Producer/Provider and turnover
* Industry Leadership
* Length of software on the market
* Software market share

**Product**

*Info: Specific KPIs (Key Performance Indicator) for the product.*

* Cost over time
* Initial Cost
* License Price
* Licensing model
* Platform hosting offering

**Corporate technology strategy for the use of the product**

* Possible uses
* Organization fit (how well the product fits into the company)
* Prototyping and development speed

Can you think of any other aspects that are important to consider? Maybe criteria that are not mentioned here?

Thank's for your help!

You can also write to me privately, if something else comes up ;)

https://redd.it/k8m3yp
@r_devops

Criteria for selecting an API gateway for a cloud environment

Hello everyone,

I am currently writing my thesis and would be very grateful for your opinions and comments.

Specifically, I'm dealing with how an API gateway can be used to secure an corporate network.

One part deals with the selection of an API gateway for a defined use case, here also with a focus on security features. I would be interested in concrete insights into the selection process in companies, how they select a API gateway and if the criteria mentioned below apply or if a certain aspect is missing.

In the following you will find a list between functional and non-functional properties:

# Functional features

**General features**

*Info: This includes general features of the product.*

* Analytics (Reports, Insides in the usage of the API)
* API technology (GraphQL, REST,.. )
* Caching
* Data security
* Error handling
* Life-Cycle Management (The ability to support different channels such as beta, test and production. This includes the ability to support multiple versions - API versioning.)
* Extensibility
* Import/Export API-definition
* Performance
* Load Balancing
* Management-API (An own API which is provided by the gateway itself for administration. For example to define new routes to services.)
* Monitoring
* Operation Model
* Payload transformation
* Logging
* Quote (Number of maximum connections per hour or other defined interval)
* Rate Limiting (Limitation of requests in a certain time interval. E.g. when providing a certain service, the customer can make 1000 requests / per hour)
* Scalability (This refers to the general ability that the product can scale depending on a certain performance)
* Redundancy (over different regions, but also redundancy in one region)

**Security features**

*Info: This includes security specific features of the product.*

* Audits (ISO 27001,9001; HIPAA; BSI C5)
* Authentication
* Authorization
* Security policies
* Thread protection
* Protocol (HTTP/HTTPS)
* Open/Closed source (the code can be viewed and checked)

# Non-functional features

**Support**

*Info: Aspects that can support the user during use.*

* Community (Developer forums, Meets-Ups,..)
* Documentation Software
* Support (commercial assistance with specific problems)
* Training (how to use the software)

**Operation**

*Info: Special aspects that can be considered when operating the product.*

* Configuration
* Usability
* Installation
* Maintenance intensity

**Producer**

*Info: This is about some aspects that concern the manufacturer and especially how the market share is.*

* Producer/Provider Eco-System
* Experience of the producer
* Size of Producer/Provider and turnover
* Industry Leadership
* Length of software on the market
* Software market share

**Product**

*Info: Specific KPIs (*Key Performance Indicator*) for the product.*

* Cost over time
* Initial Cost
* License Price
* Licensing model
* Platform hosting offering

**Corporate technology strategy for the use of the product**

* Possible uses
* Organization fit (how well the product fits into the company)
* Prototyping and development speed

Can you think of any other aspects that are important to consider? Maybe criteria that are not mentioned here?

Thank's for your help!

You can also write to me privately, if something else comes up ;)

https://redd.it/k8m3m2
@r_devops

Criteria for selecting an API gateway for a cloud environment

Hello everyone,

I am currently writing my thesis and would be very grateful for your opinions and comments.

Specifically, I'm dealing with how an API gateway can be used to secure an corporate network.

One part deals with the selection of an API gateway for a defined use case, here also with a focus on security features. I would be interested in concrete insights into the selection process in companies, how they select a API gateway and if the criteria mentioned below apply or if a certain aspect is missing.

In the following you will find a list between functional and non-functional properties:

# Functional features

**General features**

*Info: This includes general features of the product.*

* Analytics (Reports, Insides in the usage of the API)
* API technology (GraphQL, REST,.. )
* Caching
* Data security
* Error handling
* Life-Cycle Management (The ability to support different channels such as beta, test and production. This includes the ability to support multiple versions - API versioning.)
* Extensibility
* Import/Export API-definition
* Performance
* Load Balancing
* Management-API (An own API which is provided by the gateway itself for administration. For example to define new routes to services.)
* Monitoring
* Operation Model
* Payload transformation
* Logging
* Quote (Number of maximum connections per hour or other defined interval)
* Rate Limiting (Limitation of requests in a certain time interval. E.g. when providing a certain service, the customer can make 1000 requests / per hour)
* Scalability (This refers to the general ability that the product can scale depending on a certain performance)
* Redundancy (over different regions, but also redundancy in one region)

**Security features**

*Info: This includes security specific features of the product.*

* Audits (ISO 27001,9001; HIPAA; BSI C5)
* Authentication
* Authorization
* Security policies
* Thread protection
* Protocol (HTTP/HTTPS)
* Open/Closed source (the code can be viewed and checked)

# Non-functional features

**Support**

*Info: Aspects that can support the user during use.*

* Community (Developer forums, Meets-Ups,..)
* Documentation Software
* Support (commercial assistance with specific problems)
* Training (how to use the software)

**Operation**

*Info: Special aspects that can be considered when operating the product.*

* Configuration
* Usability
* Installation
* Maintenance intensity

**Producer**

*Info: This is about some aspects that concern the manufacturer and especially how the market share is.*

* Producer/Provider Eco-System
* Experience of the producer
* Size of Producer/Provider and turnover
* Industry Leadership
* Length of software on the market
* Software market share

**Product**

*Info: Specific KPIs (*Key Performance Indicator*) for the product.*

* Cost over time
* Initial Cost
* License Price
* Licensing model
* Platform hosting offering

**Corporate technology strategy for the use of the product**

* Possible uses
* Organization fit (how well the product fits into the company)
* Prototyping and development speed

Can you think of any other aspects that are important to consider? Maybe criteria that are not mentioned here?

Thank's for your help!

You can also write to me privately, if something else comes up ;)

https://redd.it/k8m3la
@r_devops

Criteria for selecting an API gateway for a cloud environment

Hello everyone,

I am currently writing my thesis and would be very grateful for your opinions and comments.

Specifically, I'm dealing with how an API gateway can be used to secure an corporate network.

One part deals with the selection of an API gateway for a defined use case, here also with a focus on security features. I would be interested in concrete insights into the selection process in companies, how they select a API gateway and if the criteria mentioned below apply or if a certain aspect is missing.

In the following you will find a list between functional and non-functional properties:

# Functional features

**General features**

*Info: This includes general features of the product.*

* Analytics (Reports, Insides in the usage of the API)
* API technology (GraphQL, REST,.. )
* Caching
* Data security
* Error handling
* Life-Cycle Management (The ability to support different channels such as beta, test and production. This includes the ability to support multiple versions - API versioning.)
* Extensibility
* Import/Export API-definition
* Performance
* Load Balancing
* Management-API (An own API which is provided by the gateway itself for administration. For example to define new routes to services.)
* Monitoring
* Operation Model
* Payload transformation
* Logging
* Quote (Number of maximum connections per hour or other defined interval)
* Rate Limiting (Limitation of requests in a certain time interval. E.g. when providing a certain service, the customer can make 1000 requests / per hour)
* Scalability (This refers to the general ability that the product can scale depending on a certain performance)
* Redundancy (over different regions, but also redundancy in one region)

**Security features**

*Info: This includes security specific features of the product.*

* Audits (ISO 27001,9001; HIPAA; BSI C5)
* Authentication
* Authorization
* Security policies
* Thread protection
* Protocol (HTTP/HTTPS)
* Open/Closed source (the code can be viewed and checked)

# Non-functional features

**Support**

*Info: Aspects that can support the user during use.*

* Community (Developer forums, Meets-Ups,..)
* Documentation Software
* Support (commercial assistance with specific problems)
* Training (how to use the software)

**Operation**

*Info: Special aspects that can be considered when operating the product.*

* Configuration
* Usability
* Installation
* Maintenance intensity

**Producer**

*Info: This is about some aspects that concern the manufacturer and especially how the market share is.*

* Producer/Provider Eco-System
* Experience of the producer
* Size of Producer/Provider and turnover
* Industry Leadership
* Length of software on the market
* Software market share

**Product**

*Info: Specific KPIs (*Key Performance Indicator*) for the product.*

* Cost over time
* Initial Cost
* License Price
* Licensing model
* Platform hosting offering

**Corporate technology strategy for the use of the product**

* Possible uses
* Organization fit (how well the product fits into the company)
* Prototyping and development speed

Can you think of any other aspects that are important to consider? Maybe criteria that are not mentioned here?

Thank's for your help!

You can also write to me privately, if something else comes up ;)

https://redd.it/k8m39a
@r_devops

Which tools do you use today for determining top recurring causes of alerts? Have these tools been effective in reducing ops pain?

In my experience, I have not found a state of the art tool that most engineers use.

https://redd.it/k8mqk4
@r_devops

Criteria for selecting an API gateway for a cloud environment

Hello everyone,

I am currently writing my thesis and would be very grateful for your opinions and comments.

Specifically, I'm dealing with how an API gateway can be used to secure an corporate network.

One part deals with the selection of an API gateway for a defined use case, here also with a focus on security features. I would be interested in concrete insights into the selection process in companies, how they select a API gateway and if the criteria mentioned below apply or if a certain aspect is missing.

In the following you will find a list between functional and non-functional properties:

# Functional features

**General features**

*Info: This includes general features of the product.*

* Analytics (Reports, Insides in the usage of the API)
* API technology (GraphQL, REST,.. )
* Caching
* Data security
* Error handling
* Life-Cycle Management (The ability to support different channels such as beta, test and production. This includes the ability to support multiple versions - API versioning.)
* Extensibility
* Import/Export API-definition
* Performance
* Load Balancing
* Management-API (An own API which is provided by the gateway itself for administration. For example to define new routes to services.)
* Monitoring
* Operation Model
* Payload transformation
* Logging
* Quote (Number of maximum connections per hour or other defined interval)
* Rate Limiting (Limitation of requests in a certain time interval. E.g. when providing a certain service, the customer can make 1000 requests / per hour)
* Scalability (This refers to the general ability that the product can scale depending on a certain performance)
* Redundancy (over different regions, but also redundancy in one region)

**Security features**

*Info: This includes security specific features of the product.*

* Audits (ISO 27001,9001; HIPAA; BSI C5)
* Authentication
* Authorization
* Security policies
* Thread protection
* Protocol (HTTP/HTTPS)
* Open/Closed source (the code can be viewed and checked)

# Non-functional features

**Support**

*Info: Aspects that can support the user during use.*

* Community (Developer forums, Meets-Ups,..)
* Documentation Software
* Support (commercial assistance with specific problems)
* Training (how to use the software)

**Operation**

*Info: Special aspects that can be considered when operating the product.*

* Configuration
* Usability
* Installation
* Maintenance intensity

**Producer**

*Info: This is about some aspects that concern the manufacturer and especially how the market share is.*

* Producer/Provider Eco-System
* Experience of the producer
* Size of Producer/Provider and turnover
* Industry Leadership
* Length of software on the market
* Software market share

**Product**

*Info: Specific KPIs (Key Performance Indicator) for the product.*

* Cost over time
* Initial Cost
* License Price
* Licensing model
* Platform hosting offering

**Corporate technology strategy for the use of the product**

* Possible uses
* Organization fit (how well the product fits into the company)
* Prototyping and development speed

Can you think of any other aspects that are important to consider? Maybe criteria that are not mentioned here?

Thank's for your help!

You can also write to me privately, if something else comes up ;)

https://redd.it/k8m5m5
@r_devops

When should I start applying for devops jobs?

Hi everyone, I have been working as a cloud engineer for 2 years now working primarily with GCP/AWS and in administration. I have three certs: GCP Professional Architect cert, AWS Solutions Architect Associate, AWS Security Specialty. I have been wanting to transition myself into devops as I believe the technology is very cool, so my question is: When should I start applying? Currently, I am scared to apply thinking I may not have all the qualifications needed. I am familiar with cloudformation & python, and have general concept knowledge of other devops tools such as kubernetes, docker, terraform, ansible, but I have not had the opportunity to work with them. I am thinking I need to get maybe an AWS Dev Associate Cert and AWS Devops Professional Cert. Then after that I could try to apply while pursuing a Certified Kubernetes Administrator and Terraform Cert. Should I start applying for jobs right now even if I know I don't meet all the prerequisites? Or should I wait till I get some additional certs before I start applying. Thank you all!

https://redd.it/k8kmkv
@r_devops