GCE Ingress in Kubernetes
Configuring GCE Ingress In Kubernetes
Last updated
Configuring GCE Ingress In Kubernetes
Last updated
To use the Google Cloud CLI for this task, and the gcloud CLI.
using the Google Cloud console or the Google Cloud CLI.
in the local environment or the machine that will be used for the deployment.
in the local environment or the machine that will be used for deployment.
Clone the GitHub repository containing the Helm charts from the or the command provided below:
git clone git@github.com:e6x-labs/helm-charts.git
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:
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.
Use the following kubectl
commands to verify that the Kubernetes resources (services & ingresses) have been created and are running as expected:
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.
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:
To create the Service, apply the manifest to the cluster by running this command:
kubectl apply -f <SERVICE_YAML_FILE>.yaml
Ingress has now been created and external tools will be able to access the e6data cluster using the configured port(s).
To enable access to multiple clusters, please repeat to create a separate service file for each e6data cluster.