Kubernetes Access

As an Oracle Backend for Parse Platform user, it is expected that you probably will not need to access the underlying infrastructure. However, if you do want to have a look around, here is how you can access the Kubernetes cluster where your Oracle Backend for Parse Platform is running.

The Oracle Backend for Parse Platform setup created a Kubernetes cluster where the server and dashboard components are deployed. At the end of setup, you were provided with a command to create a Kubernetes configuration file to access that cluster. For example:

kubeconfig_cmd = "oci ce cluster create-kubeconfig --cluster-id ocid1.cluster.oc1.iad.xxx
 --file $HOME/.kube/config --region us-ashburn-1 --token-version 2.0.0 --kube-endpoint PUBLIC_ENDPOINT"

To use the kubectl command-line interface on your local machine, you need to have the OCI CLI installed and configured.

NOTE: The generated kubeconfig file only works if you are using the DEFAULT profile in your Oracle Cloud Interface (OCI) CLI configuration file. If you are using a different OCI CLI profile, you must add --profile <NAME> to the command by editing the generated Kubernetes configuration file and add the following lines:

- --profile
- MAACLOUD

For example:

- name: user-xxxx
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - ce
      - cluster
      - generate-token
      - --cluster-id
      - ocid1.cluster....xxxx
      - --region
      - us-ashburn-1
      - --profile
      - YOUR_PROFILE_NAME
      command: oci

A simple alternative is to use the OCI Cloud Shell, which is provided in the OCI Console. You can open the OCI Cloud Shell by clicking Developer Tools in the upper right corner of the OCI Console.

Run the provided command to create your Kubernetes configuration file and then you can access the Kubernetes cluster. For example, you can list the Pods in your cluster:

Welcome to Oracle Cloud Shell.
 
Update: Cloud Shell will now use Oracle JDK 11 by default. To change this, see Managing Language Runtimes in the Cloud Shell documentation.
 
Your Cloud Shell machine comes with 5GB of storage for your home directory. Your Cloud Shell (machine and home directory) are located in: US East (Ashburn).
You are using Cloud Shell in tenancy xxxx as an OCI user xxxx
 
Type `help` for more info.
user@cloudshell:~ (us-ashburn-1)$ oci ce cluster create-kubeconfig --cluster-id ocid1.cluster.oc1.iad.xxx
 --file $HOME/.kube/config --region us-ashburn-1 --token-version 2.0.0 --kube-endpoint PUBLIC_ENDPOINT
Existing Kubeconfig file found at /home/user/.kube/config and new config merged into it
user@cloudshell:~ (us-ashburn-1)$ kubectl get pods -A
NAMESPACE         NAME                                        READY   STATUS      RESTARTS        AGE
ingress-nginx     ingress-nginx-controller-7d45557d5c-bqwwp   1/1     Running     0               4h18m
ingress-nginx     ingress-nginx-controller-7d45557d5c-klgnb   1/1     Running     0               4h18m
ingress-nginx     ingress-nginx-controller-7d45557d5c-l4d2m   1/1     Running     0               4h18m
kube-system       coredns-746957c9c6-hwnm8                    1/1     Running     0               4h27m
kube-system       csi-oci-node-kqf5x                          1/1     Running     0               4h23m
kube-system       kube-dns-autoscaler-6f789cfb88-7mptd        1/1     Running     0               4h27m
kube-system       kube-flannel-ds-hb6ld                       1/1     Running     1 (4h22m ago)   4h23m
kube-system       kube-proxy-v5qwm                            1/1     Running     0               4h23m
kube-system       proxymux-client-vpnh7                       1/1     Running     0               4h23m
parse-dashboard   kaniko                                      0/1     Completed   0               4h19m
parse-dashboard   parse-dashboard-58cb567ffd-frc4x            1/1     Running     0               4h19m
parse-server      kaniko                                      0/1     Completed   0               4h20m
parse-server      parse-server-646b97979-9pkq6                1/1     Running     0               4h19m
user@cloudshell:~ (us-ashburn-1)$

The Parse Server is running in the parse-server namespace and the Parse Dashboard is running in the parse-dashboard namespace.

Next, go to the Uninstall page to learn how to uninstall the Oracle Backend for Parse Platform.