Skip to content

blog: ensure secret pulled images #45293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

blog: ensure secret pulled images #45293

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions content/en/blog/_posts/2024-02-22-ensure-secret-pulled-images.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
layout: blog
title: 'Image Pull Policy: Configuring Kubernetes to Ensure Access Security for Container Images in a Multi-Tenant Environment'
date: 2024-02-22
slug: ensure-secret-pulled-images
---

**Authors:** Michael Brown (IBM), Paco Xu (DaoCloud)

Intro..
Copy link
Contributor

@sftim sftim Feb 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is where to talk about multitenancy use cases:

  • SaaS multitenancy, where different tenants may not be running the exact same code
  • isolating between teams in a common cluster (eg, cluster per environment; set-of-clusters per environment with tenants sharded over clusters)
  • platform-as-a-service multitenancy

etc


## Understanding Kubernetes Image Pull Policies

excerpts from : https://kubernetes.io/docs/concepts/containers/images/

## Configuring The Ensure Secret Pulled Images Featuregate

## Dependencies

## Use Cases (with feature gate enabled)

### Cluster running only non-proprietary (e.g. open-source) images. No need to hide images.

### Cluster running some proprietary images which should be hidden to those outside the company, but visible to all cluster users.

### Cluster with proprietary images, a few of which require stricter access control.

### A multi-tenant cluster where each tenant needs own private registry

## Closing Notes