Versions Compared

Old Version 1

changes.mady.by.user Vinay Krishnamurthy

Saved on

compared with

New Version Current

changes.mady.by.user Abhishek Chaturvedi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Once the kloudfuse deployment Kloudfuse installation is complete, run through the following steps if you don’t want the kloudfuse Kloudfuse stack to run with an external load balancer.

Info

Note: This has been validated for a single-node deployment so far. If you have more than one node in your deployment, please let us know.

  • Get the internal IP of the node by running kubectl get nodes -o wide. Note down the INTERNAL-IP from the output.

  • Edit the kfuse-ingress-nginx-controller-internal service by running kubectl edit service kfuse--ingress-nginx-controller-internal. Change the spec.type to ClusterIP from LoadBalancer. The spec should look like this:

...

  • Save and quit the edit session.

  • Re-edit the service spec by running kubectl edit service kfuse--ingress-nginx-controller-internal, and add the externalIPs section in spec. You’ll have to add the internal IP of the node (see first bullet point) here. The spec should now looks look like:

Code Block
spec:
  type: ClusterIP
externalIPs:
- <Node_Internal_IP>
clusterIPs:
- <Cluster_IP>
Info

Do not change/modify the clusterIPs in the spec, just add the externalIPs seciton/ section.

  • Update the security groups on your EC2 instance (from the AWS console) to allow HTTPs https traffic for the IP, which was just added. See the screenshots below on how to do it from the EC2 instance landing page.

...

You should be able to access kloudfuse Kloudfuse UI now (using the node’s external IP). And this will not go through the load balancer.

Info

Do not use the node’s internal IP to access the Kloudfuse UI. You can only access the Kloudfuse UI using the external IP.