Setting a Proxy Server for the CLI

Set up the proxy configuration for the Oracle CNE CLI.

If a proxy server is part of the environment in which a Kubernetes cluster is to be deployed, you might need to set up the proxy server configuration for the CLI. This configuration might be required for the CLI to access the Oracle Container Registry and the Kubernetes API Server. This must be performed on the host that has the CLI installed.

Set up the HTTPS_PROXY configuration.
Configure the host so container images can be pulled from the Oracle Container Registry using HTTPS. Use the format:
```
export HTTPS_PROXY=proxy_server:port
```
For example:
```
export HTTPS_PROXY=https://proxy.example.com:3128
```
Set up the NO_PROXY configuration.
Configure the host so the CLI can communicate with the Kubernetes API Server. Use the format:
```
export NO_PROXY=exclusion_list
```
For example:
```
export NO_PROXY=.example.com,127.0.0.1,localhost,169.254.169.254
```
The 169.254.169.254 IP address is reserved by many cloud providers, including OCI, as the endpoint for compute instances to access their own metadata. For more information on this IP address and how it's used, see the OCI documentation.