Versions Compared

Version Old Version 5 New Version Current
Changes made by

Subrat Sandilya

Rajeev Rai

Saved on

Key

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

...

Code Block
helm install ac5tmt adeptia/ --timeout 10m --debug -n ac5tmt

While installing you can see the status and watchlist (Needs to update your own namespace) This needs to be opened in a separate command prompt and executed.

Run the below command to see the live status of the installation:

Code Block
kubectl get pods -n  ac5tmt -w   

Run  the  below command to get pods details : 

Code Block
kubectl get pods -n  ac5tmt 

Refer to the Screenshot below : 

...

Please make sure the service status is RUNNING for all the pods.

Setting up Ingress

Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. 

Follow the given steps to Deploy [ingress-nginx]: 

Open ingress folder

...

  1. Open the ingress yaml file and change

    1. namespace: ac5tmt

    2. host: acexpress-tmt.adeptia.com

    3. host: acexpress-tmtapi.adeptia.com

    4. acexpress-tmt.adeptia.com

    5. secretName: acexpresssecret

    6. acexpress-tmtapi.adeptia.com

    7. secretName: acexpresssecret 

Refer to the below Screenshot:

...

  1. Run CMD from the ingress folder path and apply secret and ingress yaml

kubectl create secret tls acexpresssecret --key="tls.key" --cert="tls.crt" --namespace ac5tmt 
Code Block
Expand

Below is the explanation of the above command:

1. helm install

  • The install subcommand tells Helm to install a Helm chart in the Kubernetes cluster.

2. ac5tmt

  • This is the release name. Helm uses this name to manage the deployment. It acts as an identifier for the installed chart, allowing you to update, manage, or uninstall the release later.

3. adeptia/

  • Refers to the Helm chart being installed.

  • adeptia/ indicates that Helm will look for the chart named adeptia either in the local chart repository or in the configured Helm repositories.

4. --timeout 10m

  • Sets a timeout of 10 minutes for the installation process.

  • If the deployment takes longer than 10 minutes, Helm will terminate the process and report a failure.

5. --debug

  • Enables debug mode, providing detailed logs and additional information during the installation process. Useful for troubleshooting if the deployment encounters issues.

6. -n ac5tmt

  • Specifies the namespace where the release should be installed (ac5tmt).

  • Kubernetes namespaces allow you to organize resources logically within a cluster.

While installing you can see the status and watchlist (Needs to update your own namespace) This needs to be opened in a separate command prompt and executed.

Run the below command to see the live status of the installation:

Code Block
kubectl get pods -n  ac5tmt -w   

Run  the  below command to get pods details : 

Code Block
kubectl get pods -n  ac5tmt 

Refer to the Screenshot below : 

...

Please make sure the service status is RUNNING for all the pods.

...

Setting up Ingress

Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. 

Follow the given steps to Deploy [ingress-nginx]: 

Open ingress folder

...

  1. Open the ingress yaml file and change

    1. namespace: ac5tmt

    2. host: acexpress-tmt.adeptia.com

    3. host: acexpress-tmtapi.adeptia.com

    4. acexpress-tmt.adeptia.com

    5. secretName: acexpresssecret

    6. acexpress-tmtapi.adeptia.com

    7. secretName: acexpresssecret 

Refer to the below Screenshot:

...

  1. Run CMD from the ingress folder path and apply secret and ingress yaml

Code Block
kubectl create secret tls acexpresssecret --key="tls.key" --cert="tls.crt" --namespace ac5tmt 
Expand
titleClick Here For More Details

1. kubectl create secret tls

  • kubectl: The Kubernetes command-line tool used to interact with the Kubernetes API.

  • create secret tls: Tells Kubernetes to create a secret of type tls. TLS secrets are used to store SSL/TLS certificates and keys.

2. acexpresssecret

  • The name of the secret. This will be referenced in your deployments or services to enable secure communications (like HTTPS).

3. --key="tls.key"

  • Specifies the path to the private key file (tls.key). This file contains the private key used for SSL/TLS encryption.

4. --cert="tls.crt"

  • Specifies the path to the certificate file (tls.crt). This file contains the public certificate that corresponds to the private key.

5. --namespace ac5tmt

  • Specifies the namespace (ac5tmt) in which the secret will be created. Namespaces help organize resources in a cluster.

This will create a secret in the namespace

...

Go to services, Ingress, and get the external IP

...

Bind the IP with DNS ac4tmtac5tmt.adeptia.com

Example: https://acexpress-ist-poc.adeptia.com/Portal2/#/home

...