When a cluster's Kubernetes API endpoint has a public IP address, you can access the cluster in Cloud Shell by setting up a kubeconfig file

Generating an API signing key pair is a mandatory step while setting up cluster access using local machine if the public key is not already uploaded in the console.

To access the cluster using kubectl you have to set up a Kubernetes manifest file for the cluster. The kubeconfig file by default is named config and stored in the $HOME/.manifest directory

To access the cluster using kubectl you have to set up a Kubernetes configuration file for the cluster. The kubeconfig file by default is named config and stored in the $HOME/.kube directory.

You cannot setup Cloud shell access to the cluster if the clusters Kubernetes API end-point has a private IP address.

Continuous delivery requires more automatic linting, while continuous deployment testing must be run manually.

Continuous delivery utilizes automatic deployment to a development environment, while continuous deployment involves automatic deployment to a production environment.

Continuous delivery involves automation of developer tasks, while continuous deploy-ment involves manual operational tasks.

Continuous delivery is a process that initiates deployment manually, while continuous deployment is based on automating the deployment process.