Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

Latest commit

 

History

History
56 lines (36 loc) · 1.3 KB

connecting-to-wcms-container.md

File metadata and controls

56 lines (36 loc) · 1.3 KB

Connecting to a WCMS container

The WCMS Kubernetes environment requires use of the kubectl command. Details on installation/configuration are available from the WCMS team.

This document describes common kubectl commands useful for administrative tasks.

Set the WCMS environment context

Our environments are named:

  • dev02
  • test02
  • stage01
  • TODO prod

To set the environment for the current Windows shell:

kubectl config use-context ocio-wcms-ENVNAME-eks

For the dev02 environment, for example:

> kubectl config use-context ocio-wcms-dev02-eks

All subsequent kubectl commands will use the current context, until you change it.

List all pods in an environment

To list all the pods in a environment context:

> kubectl get pods -o wide

Tail all the logs in an environment

To tail all the running pods:

> kubectl logs -f --selector app=arpa-ui

Connect to a running container with bash

First, get a pod identifier by listing all the pods. The identifiers are the first NAME column and typically start with arpa-ui-. You only need one them. Any one will do. These identifiers change on every deployment.

Second, execute the bash command on one of the pods:

> kubectl exec -it :podidentifier: -- bash