This article provides an easy way to patch the Veeam Kasten for Kubernetes operand and make changes to the Veeam Kasten for Kubernetes configuration in an operator-based installation.
Veeam Kasten for Kubernetes is available for installation in an OCP cluster through either helm charts or the Red Hat Marketplace operator.
When using helm, configuration changes to Veeam Kasten for Kubernetes can be made through helm upgrades, which support using either a values file or helm values as arguments with --set or --set-string.
On the other hand, the K10 operator is a helm-based operator that allows the configuration of Veeam Kasten for Kubernetes values using an operand CR called k10s.apik10.kasten.io. Updating the Veeam Kasten for Kubernetes configuration requires modifying this resource.
However, this resource is a large file with over a thousand lines, making manual editing extremely difficult. This article aims to provide a more straightforward method for modifying the contents of the K10 operand using the kubectl patch.
Below are examplesdemonstrating how to enable OpenShift OAuth integration in Veeam Kasten for Kubernetes with helm and operator-based installation.
Run the following command with the specified values provided as helm arguments using the _--set_parameter.
helm install k10 kasten/k10 --namespace=kasten-io \
--set scc.create=true \
--set route.enabled=true \
--set route.tls.enabled=true \
--set auth.openshift.enabled=true \
--set auth.openshift.serviceAccount=k10-dex-sa \
--set auth.openshift.clientSecret=${DEX_TOKEN} \
--set auth.openshift.dashboardURL=https://k10-route-kasten-io.${APPS_BASE_DOMAIN}/k10/ \
--set auth.openshift.openshiftURL=https://${API_BASE_DOMAIN}:6443 \
--set auth.openshift.insecureCA=true
Copy
Alternatively, the following values can be specified in a YAML file and used for upgrade.
# values.yaml
scc:
create: true
route:
enabled: true
tls:
enabled: true
auth:
openshift:
enabled: true
serviceAccount: k10-dex-sa
clientSecret: ${DEX_TOKEN}
dashboardURL: https://k10-route-kasten-io.${APPS_BASE_DOMAIN}/k10/
openshiftURL: https://${API_BASE_DOMAIN}:6443
insecureCA: true
Copy
Veeam Kasten for Kubernetes instance can be upgraded using the following helm upgrade command, assuming the above values are saved in the values.yaml file.
helm upgrade k10 --namespace kasten-io -f values.yaml
Copy
Making the same changes mentioned above by editing the Veeam Kasten for Kubernetes operand can be a bit cumbersome. The Veeam Kasten for Kubernetes operand manifest contains the values for configuring Veeam Kasten for Kubernetes, following a similar schema as the helm values file.
All the values are listed under a top-level object called spec. For example, if the helm values used scc.create, it would be spec.scc.create in the operand. Similarly, route.enabled in helm would be spec.route.enabled in the operand.
Hence, the provided patch file can be used to configure the same values in the Veeam Kasten for Kubernetes operator.
#patch.yaml
spec:
scc:
create: true
route:
enabled: true
tls:
enabled: true
auth:
openshift:
enabled: true
serviceAccount: k10-dex-sa
clientSecret: ${DEX_TOKEN}
dashboardURL: https://k10-route-kasten-io.${APPS_BASE_DOMAIN}/k10/
openshiftURL: https://${API_BASE_DOMAIN}:6443
insecureCA: true
Copy
To upgrade the K10 operator-based installation, following patch command can be used, assuming the above values are saved in the patch.yaml
file.
kubectl patch k10s.apik10.kasten.io k10 -n kasten-io --type=merge --patch-file patch.yaml
Copy
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.