End-to-End Kubernetes with Rancher, RKE2, K3s, Fleet, Longhorn, and NeuVector

GitRepoRestrictions: A Granular Workspace-Level Access Control

At a more granular level, Fleet allows you to define restrictions on GitRepo resources using GitRepoRestrictions. This feature is useful when you want to control the allowed RepoPatterns, ServiceAccounts, ClientSecrets, and TargetNamespaces for a GitRepo resource.

For example, if our goal is to restrict the user developer to only use the todo-app-namespace target namespace in the dev workspace, we can create a GitRepoRestriction resource:

cat <
kind: GitRepoRestriction
apiVersion: fleet.cattle.io/v1alpha1
metadata:
  name: restricted-to-todo-app-namespace
  namespace