1"use strict";(self.webpackChunkvcluster_docs=self.webpackChunkvcluster_docs||[]).push([["13739"],{25915(e,t,s){s.r(t),s.d(t,{metadata:()=>r,default:()=>h,frontMatter:()=>c,contentTitle:()=>o,toc:()=>l,assets:()=>i});var r=JSON.parse('{"id":"understand/what-are-secrets","title":"What are Secrets","description":"What are Secrets?","source":"@site/platform_versioned_docs/version-4.12.0/understand/what-are-secrets.mdx","sourceDirName":"understand","slug":"/understand/what-are-secrets","permalink":"/docs/platform/understand/what-are-secrets","draft":false,"unlisted":false,"editUrl":"https://github.com/loft-sh/vcluster-docs/edit/main/platform_versioned_docs/version-4.12.0/understand/what-are-secrets.mdx","tags":[],"version":"4.12.0","sidebarPosition":9,"frontMatter":{"title":"What are Secrets","sidebar_label":"What Are Secrets","sidebar_position":9},"sidebar":"siteSidebar","previous":{"title":"What Are Stacks","permalink":"/docs/platform/understand/what-are-stacks"},"next":{"title":"What Are Users and Teams","permalink":"/docs/platform/understand/what-are-users-and-teams"}}'),a=s(74848),n=s(28453);let c={title:"What are Secrets",sidebar_label:"What Are Secrets",sidebar_position:9},o,i={},l=[{value:"What are Secrets?",id:"what-are-secrets",level:2},{value:"Project Secrets",id:"project-secrets",level:2},{value:"Global Secrets",id:"global-secrets",level:2}];function d(e){let t={a:"a",h2:"h2",p:"p",...(0,n.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(t.h2,{id:"what-are-secrets",children:"What are Secrets?"}),"\n",(0,a.jsxs)(t.p,{children:["Like ",(0,a.jsx)(t.a,{href:"https://kubernetes.io/docs/concepts/configuration/secret/",children:"Kubernetes secrets"}),", vCluster Platform secrets are intended to hold confidential data in the form of key/value pairs. vCluster Platform extends Kubernetes secrets by allowing global or project level management of secret data, managing which users and teams can access secrets, and synchronizing secret data across multiple clusters and the spaces and tenant clusters on those clusters. After creating vCluster Platform secrets, native Kubernetes secrets can be created with labels that indicate to vCluster Platform that the secret data should be synchronized with vCluster Platform secrets. Once this secret synchronization is configured, the secret data can be mounted using the native secret as usual, but managed at the project or global level using vCluster Platform secrets."]}),"\n",(0,a.jsx)(t.h2,{id:"project-secrets",children:"Project Secrets"}),"\n",(0,a.jsxs)(t.p,{children:["Project secrets are scoped to a Project, and implicitly only allow access to members of the project. Once a project secret is created, native Kubernetes secrets that synchronize to the project secret can be created in spaces and tenant clusters that belong to the project. This provides a convenient way to manage secret data for all members of the project. For more information on creating project secrets, see ",(0,a.jsx)(t.a,{href:"/docs/platform/administer/secrets/project/create",children:"creating project secrets"})]}),"\n",(0,a.jsx)(t.h2,{id:"global-secrets",children:"Global Secrets"}),"\n",(0,a.jsxs)(t.p,{children:["Global secrets or shared secrets can be synchronized across all spaces in vCluster Platform registered clusters. Additionally, global secrets can be use to synchronize project secrets. This allows organization wide management of secrets shared across multiple projects. Like project secrets, native Kubernetes secrets can be synchronized directly to global secrets, however this synchronization only works for secrets defined in spaces and not tenant clusters. For more information on creating project secrets, see ",(0,a.jsx)(t.a,{href:"/docs/platform/administer/secrets/global/create",children:"creating global secrets"})]})]})}function h(e={}){let{wrapper:t}={...(0,n.R)(),...e.components};return t?(0,a.jsx)(t,{...e,children:(0,a.jsx)(d,{...e})}):d(e)}},28453(e,t,s){s.d(t,{R:()=>c,x:()=>o});var r=s(96540);let a={},n=r.createContext(a);function c(e){let t=r.useContext(n);return r.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function o(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(a):e.components||a:c(e.components),r.createElement(n.Provider,{value:t},e.children)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.