TLS Protect for Kubernetes
Log inCreate account
Important Announcement!

This deprecated version of TLS Protect for Kubernetes, originally known as Jetstack Secure, will be PERMANENTLY SHUTDOWN on May 19, 2025. If you're still using this version, please work with your CyberArk/Venafi account team to transition to the current version of TLS Protect for Kubernetes.

Cleaning up

To finish let's clean up

  • Remove the Ingress resource for the application
  • Remove the service and the deployment
  • Remove the Certificate resource
  • Remove the secret that contains the token for the issuer
  • Remove the issuer
  • Remove the namespace
kubectl -n jss-academy delete Ingress hello-jss-ingress
kubectl -n jss-academy delete svc hello-jss-svc
kubectl -n jss-academy delete deploy hello-jss-app
kubectl -n jss-academy delete Certificate hello-jss.REPLACE_WITH_YOUR_DOMAIN_NAME
kubectl -n jss-academy delete secret access-token-for-tpp
kubectl -n jss-academy delete issuer academy-issuer
kubectl delete ns jss-academy
Copy to clipboard

The TLS Protect for Kubernetes Agent periodically tracks changes to your cluster and on the next poll, will not show the deleted resources in the dashboard anymore. To validate, wait for a couple of minutes and log back into the TLS Protect for Kubernetes dashboard.

In the next course, let's look at the alerting capabilities in TLS Protect for Kubernetes

On this page