If you have an existing Edge site installation without classification, you can enable it afterwards. Similarly, you can disable classification on installation where it is enabled.
Note Enabling or disabling classification can take a few minutes before the changes are in effect.
Note The following commands have been updated with the 2023.02 release. While these commands will work for all previous and new Edge site versions, the old commands will not work for any newly installed sites with version 2023.02 or later.
Enable classification
- K3S
- EKS
To enable classification on an existing Edge site, deployed on K3S, run this command:
POD_NAME=$(sudo /usr/local/bin/kubectl get pod -n collibra-edge -l app.kubernetes.io/component=application-controller -o name)
sudo /usr/local/bin/kubectl -n collibra-edge exec -it ${POD_NAME} \ -- bash -c 'argocd admin cluster kubeconfig https://kubernetes.default.svc \ /tmp/config --namespace collibra-edge ; env KUBECONFIG=/tmp/config argocd app set collibra-edge --core -p collibra.classification.enabled=true'
To enable classification on an existing Edge site, deployed on EKS, run this command:
POD_NAME=$(kubectl get pod -n collibra-edge -l app.kubernetes.io/component=application-controller -o name)
kubectl -n collibra-edge exec -it ${POD_NAME} \ -- bash -c 'argocd admin cluster kubeconfig https://kubernetes.default.svc \ /tmp/config --namespace collibra-edge ; env KUBECONFIG=/tmp/config argocd app set collibra-edge --core -p collibra.classification.enabled=true'
Disable classification
- K3S
- EKS
To disable classification on an existing Edge site, deployed on K3S, run this command:
POD_NAME=$(sudo /usr/local/bin/kubectl get pod -n collibra-edge -l app.kubernetes.io/component=application-controller -o name)
sudo /usr/local/bin/kubectl -n collibra-edge exec -it ${POD_NAME} \ -- bash -c 'argocd admin cluster kubeconfig https://kubernetes.default.svc \ /tmp/config --namespace collibra-edge ; env KUBECONFIG=/tmp/config argocd app set collibra-edge --core -p collibra.classification.enabled=false'
Tip The only difference between disabling classification and enabling classification is that the last argument is false instead of true.
To disable classification on an existing Edge site, deployed on EKS, run this command:
POD_NAME=$(kubectl get pod -n collibra-edge -l app.kubernetes.io/component=application-controller -o name)
kubectl -n collibra-edge exec -it ${POD_NAME} \ -- bash -c 'argocd admin cluster kubeconfig https://kubernetes.default.svc \ /tmp/config --namespace collibra-edge ; env KUBECONFIG=/tmp/config argocd app set collibra-edge --core -p collibra.classification.enabled=false'
Tip The only difference between disabling classification and enabling classification is that the last argument is false instead of true.
Successful execution of either command returns the following output:
INFO[0000] Starting configmap/secret informers INFO[0000] Configmap/secret informer synced
Note You do not need to restart Edge when you have enabled or disabled classification.