---
title: "Hazem Khairy (@hazem0h) | Hashnode"
description: "DevOps Engineer. Read the latest articles by Hazem Khairy on Hashnode."
url: "https://hashnode.com/@hazem0h"
---

@hazem0h

# Hazem Khairy

@hazem0h · Joined April 2022

DevOps Engineer

### [Terraform's Ephemeral Values](https://hazemkh.hashnode.dev/terraform-s-ephemeral-values?utm_source=hashnode&utm_medium=feed)

Terraform's 𝑬𝒑𝒉𝒆𝒎𝒆𝒓𝒂𝒍 values let you avoid persisting many sensitive credentials in state. Many people mitigate Terraform state secret leakage by encrypting the remote state. For example, a v

1 min read · [hazemkh.hashnode.dev](https://hazemkh.hashnode.dev/terraform-s-ephemeral-values?utm_source=hashnode&utm_medium=feed)

[Jul 12](https://hashnode.com/posts/terraform-s-ephemeral-values/6a53f7b15164f167213d9a65)

### [Skopeo: Push Container Images without Privileged Access:](https://hazemkh.hashnode.dev/skopeo-push-container-images-without-privileged-access?utm_source=hashnode&utm_medium=feed)

Want to Push Container Images Without Docker or Privileged Access? Use Skopeo If you need to move container images between registries, the common approach is: docker pull <source-registry>/image:tag d

2 min read · [hazemkh.hashnode.dev](https://hazemkh.hashnode.dev/skopeo-push-container-images-without-privileged-access?utm_source=hashnode&utm_medium=feed)

[Apr 26](https://hashnode.com/posts/skopeo-push-container-images-without-privileged-access/69ee790d3d6a492cdd4cb763)

### [Nginx isn’t dead, Ingress-Nginx is](https://hazemkh.hashnode.dev/nginx-isn-t-dead-ingress-nginx-is?utm_source=hashnode&utm_medium=feed)

Ingress-nginx retirement Last November, we saw that ingress-nginx is heading toward retirement. That does not mean NGINX itself is going away. That’s not true at all. Nginx vs Ingress-Nginx vs Kuberne

2 min read · [hazemkh.hashnode.dev](https://hazemkh.hashnode.dev/nginx-isn-t-dead-ingress-nginx-is?utm_source=hashnode&utm_medium=feed)

[Apr 10](https://hashnode.com/posts/nginx-isn-t-dead-ingress-nginx-is/69d8a86d075944a59145b5f4)

### [No, Big O notation is not equivalent to saying "worst case scenario"](https://hazemkh.hashnode.dev/no-big-o-notation-is-not-equivalent-to-saying-worst-case-scenario?utm_source=hashnode&utm_medium=feed)

Each type of analysis (worst case, or best case) can have its own upper bound (Big O), lower bound (Big Omega), and tight bound (Big Theta).

3 min read · [hazemkh.hashnode.dev](https://hazemkh.hashnode.dev/no-big-o-notation-is-not-equivalent-to-saying-worst-case-scenario?utm_source=hashnode&utm_medium=feed)

[Sep 21, 2022](https://hashnode.com/posts/no-big-o-notation-is-not-equivalent-to-saying-worst-case-scenario/632b2192c63fa0e8e95a7a88)
