Skip to content

Latest commit

 

History

History
122 lines (85 loc) · 6.19 KB

kubernetes.md

File metadata and controls

122 lines (85 loc) · 6.19 KB
copyright lastupdated keywords subcollection
years
2020, 2023
2023-03-09
command-line interface, kubernetes and code engine cli, knative and code engine cli, kubectl and code engine cli, kubernetes, knative
codeengine

{{site.data.keyword.attribute-definition-list}}

Using Kubernetes with {{site.data.keyword.codeengineshort}}

{: #kubernetes}

{{site.data.keyword.codeenginefull}} is designed so that you do not need to interact with the underlying technology it is built upon. However, if you have existing tools that are based on Kubernetes or Knative, you can still use it with {{site.data.keyword.codeengineshort}}. {{site.data.keyword.codeengineshort}} supports the Kubernetes (and Knative) APIs and their CLI commands. For more information about Knative, see Using Knative with Code Engine. {: shortdesc}

If you decide to use Kubernetes with {{site.data.keyword.codeengineshort}}, consider the following:

  • Most containers or pods that run on Kubernetes also run on {{site.data.keyword.codeengineshort}}.
  • Kubernetes constructs, such as deployments, run on {{site.data.keyword.codeengineshort}} if they do not use cluster-wide capabilities, such as security policies. {{site.data.keyword.codeengineshort}} is scoped to what can run in a Kubernetes namespace.

{{site.data.keyword.codeengineshort}} does not support OpenShift-specific resources or other container orchestration platforms, such as Docker Swarm or Compose Swarm.

Installing the Kubernetes command-line interface

{: #kubernetes-kubectl}

To install the Kubernetes CLI, download and install the kubectl CLI{: external}. {: shortdesc}

Be sure to add the kubectl binary to your system's PATH environment variable. {: tip}

Interacting with Kubernetes API

{: #kubectl-kubeconfig}

To interact with your project from the Kubernetes command-line interface, kubectl, or with Knative, kn you must set up your environment to interact with the Kubernetes API of {{site.data.keyword.codeengineshort}}.

Before you begin

You can set up your environment in the following ways.

  • You can add the --kubecfg option to your project select command. For example,

    ibmcloud ce project select --name PROJECT_NAME --kubecfg

    {: pre}

  • You can export the kubeconfig file directly. Run the ibmcloud ce project current command to find the project that you are currently targeting. This command also returns the export command for your kubeconfig file. For example,

    ibmcloud ce project current

    {: pre}

    Example output

    Getting the current project context...
    OK
    
    Name:       myproject
    ID:         01234567-abcd-abcd-abcd-abcdabcd1111
    Subdomain:  aabon2dfwa0
    Domain:     us-south.codeengine.appdomain.cloud
    Region:     us-south
    Kubectl Context:  4svg40kna19
    
    Kubernetes Config:
    Context:             aabon2dfwa0
    Environment Variable: export KUBECONFIG=/user/myusername/.bluemix/plugins/code-engine/myproject-01234567-abcd-abcd-abcd-abcdabcd1111.yaml

    {: screen}

    Then, copy the export command, paste it into your command-line interface, and run it.

Verify that your environment is set correctly by running the kubectl config command.

kubectl config current-context

{: pre}

If the context is correctly set, the output matches the Kubectl Context value of your project. For example, if your Kubectl Context value of your project is 4svg40kna19, the command returns 4svg40kna19.

For more information about Kubernetes and how it works with {{site.data.keyword.codeengineshort}} architecture, see Learning about {{site.data.keyword.codeengineshort}} architecture and workload isolation. {: important}

Required access authorities to work with Kubernetes API

{: #kubectl-api}

After you set up your environment, you can interact with Kubernetes API. You must have the correct level of authority for specific tasks. These roles are set in Identity and access management. See {{site.data.keyword.cloud_notm}} service roles.

Resource Manager role Writer role Reader role
serviceaccounts get, list, watch get, list, watch None
secrets get, list, watch, create, delete, update, patch, apply, edit get, list, watch, create, delete, update, patch, apply, edit None
configmaps get, list, watch, create, delete, update, patch, apply, edit get, list, watch, create, delete, update, patch, apply, edit None
events get, list, watch get, list, watch None
pods/log get, list, watch get, list, watch get, list, watch
pods get, list, watch, create, delete, patch, apply get, list, watch, create, delete, patch, apply get, list, watch
services get, list, watch, create, delete, patch, apply get, list, watch, create, delete, patch, apply get, list, watch
pods/exec create create None
pods/portforward create create None
pods/attach create None None
pods/status get, list get, list None
resourcequotas get, list, watch get, list, watch get, list, watch
limitranges get, list, watch get, list, watch None
deployments get, list, watch, create, delete, patch, apply get, list, watch, create, delete, patch, apply get, list, watch
daemonset get, list, watch get, list, watch get, list, watch
pods.metrics.k8s.io list list list
{: caption="Table 1. Kubernetes authorities" caption-side=ottom"}