<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>scc on My learning and diary</title>
    <link>https://jackliusr.github.io/tags/scc/</link>
    <description>Recent content in scc on My learning and diary</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 16 Jul 2026 20:00:00 +0800</lastBuildDate><atom:link href="https://jackliusr.github.io/tags/scc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Run a Pod with a Fixed UID Outside the Default OpenShift UID Range</title>
      <link>https://jackliusr.github.io/posts/2026/07/how-to-run-a-pod-with-a-fixed-uid-outside-the-default-openshift-uid-range/</link>
      <pubDate>Thu, 16 Jul 2026 20:00:00 +0800</pubDate>
      
      <guid>https://jackliusr.github.io/posts/2026/07/how-to-run-a-pod-with-a-fixed-uid-outside-the-default-openshift-uid-range/</guid>
      <description>OpenShift enhances container security by assigning a random, non-root User ID (UID) to workloads by default. This helps isolate workloads running in different namespaces and prevents containers from running with predictable user IDs.
 While this security model works well for cloud-native applications, some third-party or legacy container images expect to run with a specific UID. A common example is the nginxinc/nginx-unprivileged image, which expects to run as UID 101.</description>
    </item>
    
  </channel>
</rss>
