Readme file

        Version last updated: 12/01/2022

        CloudHedge Appliance helm chart

        CloudHedge is a automation tool that enable enterprise and ISVs to containerize their workloads on any flavour of kubernetes. In addition, to speed up and automate the containerization of Windows, Linux, and AIX based workloads within weeks.

        Using AI, CloudHedge can analyze your existing applications, and automatically recommend and transform monolith applications to cloud-native.

        CloudHedge not only support Lift-Shift model but it can also Re-Factor and containerize automatically !

        CloudHedge runs as a SAAS. It can also be deployed in your environment as a CloudHedge Enterprise. Additional documentation for the product can be found here.

        This helm chart is hosted and managed by CloudHedge Engineers

        For any query or help reach out to us @ hello@cloudhedge.io

        Introduction

        CloudHedge charts for Helm are carefully engineered, maintained and are the quickest and easiest way to deploy CloudHedge Enterprise on a any flavour of Kubernetes cluster that are ready to handle production workloads.

        This chart sets up a CloudHedge Enterprise on a Kubernetes cluster using the Helm package manager.

        Prerequisites

        • The mongoDB is setup as per the instructions
        • The NFS is setup and enabled as per the instructions (optional step)
        • The various settings are updated in values.yaml as described bellow.
        • Kubernetes 1.12+
        • Helm 3.1.0

        Parameters

        The following tables lists the configurable parameters of the CloudHedge Enterprise chart and their default values per section/component:

        Database Params

        Parameter Description Default Required
        db.dbUser MongoDB Username nil Yes
        db.dbPassword MongoDB Password nil Yes
        db.dbUrl MongoDB URL with port number. This URL should be reachable from all Cloudhedge Enterprise Pods nil Yes
        db.dbName MongoDB Database name nil Yes
        db.dbProto MongoDB Protocol mongodb NO

        Global parameters

        Parameter Description Default Required
        global.image.registry Global Container image registry registry.connect.redhat.com/cloudhedge No
        global.image.tag Global Container image tag ch-rel-1.3.3 No
        global.image.imagePullSecrets Global Container registry secret names as an array [] (does not add image pull secrets to deployed pods) No
        global.image.username All CloudHedge component images are available in private repository. One can give username and password of the registry to pull the images. This helm chart creates a docker secret for you. Set value = docker registry username nil No
        global.image.password All CloudHedge component images are available in private repository. One can give username and password of the registry to pull the images. This helm chart creates a docker secret for you. Set value = docker registry password nil No
        global.webappExposeType How to expose the webapp? Possible values are: LoadBalancer, ClusterIP and NodePort LoadBalancer No
        global.webappProtocol How Webapp is exposed HTTP No
        global.jwtSecret JWT secret value, give a random string. this string is used to encrypt JWT token theJWTSuperSecretValue No
        global.encryptSecret random string. this sting is used to encrypt sensitive data in DB theEncryptSuperSecretValue No
        global.commonLabels Labels need to attach with every deployed object {} No
        global.commonAnnotations Annotations need to attach with every deployed object {} No

        Common parameters

        Parameter Description Default Required
        nameOverride String to partially override "" No
        fullnameOverride String to fully override "" No
        elkHost Cloudhedge Enterprise can push the logs to elk. Give full qualified and reachable elk URL "" No
        appHost exposed URL of the webapp. This URL should be reachable from discover box and build box "" No

        Install helm chart

        Adding the Helm Repository

        This step is required if you’re installing the chart via the helm repository.

        helm repo add cloudhedge https://cloudhedge.github.io/ch-appliance-helm3-chart/
helm update

        Verify that helm repository gets added by running the command.

        helm repo list

        List all available version of CloudHedge helm charts by running a command,

        helm search repo cloudhedge

        This command output should show all available versions of CloudHedge helm charts

        Setup CloudHedge Appliance

        Passing params via command line.

        Specify parameter using the --set key=value,key=value argument to helm install command For example,

        $ helm install ch-appliance \
  --set db.dbUser= \
  --set db.dbPassword= \
  --set db.dbUrl= \
  --set db.dbName= \
  --set db.dbProto= \
  --set global.image.username= \
  --set global.image.password= \
  --set global.webappProtocol=HTTPS \
  cloudhedge/ch-appliance-helmchart

        Make sure to use correct db credentials by replacing with correct values

        Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

        $ helm install ch-appliance -f values.yaml cloudhedge/ch-appliance-helmchart

        You can use the default values.yaml. The file has enough pointers for each possible parameter. Update this file and run mansioned commnad

        Getting support

        CloudHedge Support Plans are based on the subscription model or on the number of licenses purchased by our customers. Responses to support issues are typically provided approximately 1 to 2 business days.

        If you run through issues, you can contact +91-20-67994020 from 9am to 5pm CST or drop in an Email to support@cloudhedge.io

        Support Locations:
        India, United States