GCE Ingress in Kubernetes

Configuring GCE Ingress In Kubernetes

Prerequisites

• Enable GCE Ingress Controller

• Enable the Google Kubernetes Engine API

• To use the Google Cloud CLI for this task, install and initialize the gcloud CLI.

• Enable the HttpLoadBalancing add-on using the Google Cloud console or the Google Cloud CLI.

• kubectlshould be installed in the local environment or the machine that will be used for the deployment.

• Helm should be installed in the local environment or the machine that will be used for deployment.

Install GCE Ingress using a Helm chart (recommended)

Configure the Helm Chart

1. Clone the GitHub repository containing the Helm charts from the GitHub URL or the command provided below:

   git clone [e-mail]:e6x-labs/helm-charts.git

2. Customize Chart Values: Navigate to the cloned Helm chart directory (./charts/ingress/ ) and modify the values in the values.yaml file or create a custom value file.

   • This file contains configuration options that customize the behavior of the chart during deployment. You can adjust parameters such as the image version, service type, ingress settings, etc., based on your requirements.

   • It is mandatory to edit the following values in the values.yaml file:

cloud: <CLOUD_PROVIDER>
alias: <ALIAS_NAME>
workspace: <WORKSPACE_NAME>
cluster: <CLUSTER_NAME>

Deploy the Helm Chart

Use the helm install command to deploy the Helm chart. Provide a release name for the deployment and specify the path to the chart directory. For example:

helm install <RELEASE_NAME> ./charts/ingress/

The above command deploys the Helm chart with <RELEASE_NAME> using the configuration from the ./charts/ingress/ directory.

<RELEASE_NAME> can be set to any value.

Verify Deployment

Use the following kubectl commands to verify that the Kubernetes resources (services & ingresses) have been created and are running as expected:

kubectl get services -n <E6DATA_NAMESPACE>
kubectl get ingress -n <E6DATA_NAMESPACE>

If the Ingress resource has been set up correctly and the e6data engine is exposed externally, external tools & services can now connect to it using the configured hostname or IP address.

A Personal Access Token is required for authentication.

Create Service

A separate Service should be created for each e6data cluster (if external access is required for multiple clusters).

Create a service file, following the example below:

847B

e6data-ext-access-service-gce.yaml

Sample e6data-ext-access-service-gce.yaml

e6data-ext-access-service-gce.yaml

apiVersion: v1
kind: Service
metadata:
  name: e6data-ext-access-cluster1  # edit as required
  namespace: <E6DATA_NAMESPACE> # change to e6data workspace namespace
  labels:
    cloud: <CLOUD_PROVIDER>
    alias: <ALIAS>
    workspace: <WORKSPACE_NAME>
    cluster: <CLUSTER_NAME>
  annotations:
    networking.gke.io/whitelist: "<IP(S)_TO_BE_ALLOWLISTED>"
    networking.gke.io/managed-certificates: "<ARN(S)_OF_CERT(S)>"
spec:
  type: LoadBalancer
  selector:
    cloud: <CLOUD_PROVIDER>
    alias: <ALIAS>
    workspace: <WORKSPACE_NAME>
    cluster: <CLUSTER_NAME>
  ports:
  - protocol: TCP
    port: 9000                  # external access port, edit as required
    targetPort: http            # change to HTTPS if SSL certificate is used
    name: http                  # change to HTTPS if SSL certificate is used

To create the Service, apply the manifest to the cluster by running this command:

kubectl apply -f <SERVICE_YAML_FILE>.yaml

To enable access to multiple clusters, please repeat the above steps to create a separate service file for each e6data cluster.

Ingress has now been created and external tools will be able to access the e6data cluster using the configured port(s).