Solved

Creating k10Profiles/Policy with yaml

Forum|Forum|2 years ago
April 26, 2023
3 comments
193 views

markbon
Comes here often

When i create a profile/policy for k10 as yaml does this resource have to be in the kasten-io namespace or can they be defined in any namespace? e.g. “my-namespace”

apiVersion: config.kio.kasten.io/v1alpha1kind: Profilemetadata:  name: sample-profile  namespace: my-namespace

apiVersion: config.kio.kasten.io/v1alpha1kind: Policymetadata:  name: sample-backup-policy  namespace: my-namespace

What about the secret necessary for the profile? Can this be definded outside the kasten-io namespace ?

Thx in advance ;)

Best answer by jaiganeshjk

@markbon Thank you for posting your question here.

K10 requires profiles to be there in the namespace as the K10 is installed(By default it is kasten-io)

If you have installed K10 in a namespace called kasten-io, Profile resources are expected to be in kasten-io namespace.

However, Policies are allowed to be created in other namespaces. We call them application-scoped policies. This is to allow non-admin users to create policies for their namespaces,

Do you have a specific use-case to create profile out of K10s namespace ?

+21

Chris.Childerhose
Veeam Legend, Veeam Vanguard
Forum|Forum|2 years ago
April 26, 2023

@jaiganeshjk @Geoff Burke

Like

+2

jaiganeshjk
Experienced User
Answer
Forum|Forum|2 years ago
April 26, 2023

@markbon Thank you for posting your question here.

K10 requires profiles to be there in the namespace as the K10 is installed(By default it is kasten-io)

If you have installed K10 in a namespace called kasten-io, Profile resources are expected to be in kasten-io namespace.

However, Policies are allowed to be created in other namespaces. We call them application-scoped policies. This is to allow non-admin users to create policies for their namespaces,

Do you have a specific use-case to create profile out of K10s namespace ?

Jaiganesh

M