Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Instructions

  1. https://github.com/egovernments/eGov-infraOps/ 

    1. Add service manifests cluster/app/egov/<module>/<service-name>.yml

    2. Add configMap if any cluster/conf/configMaps.yml

       

    3. Add encrypted credentials if any cluster/conf/secrets.yml

       

    4. Provision the volumes and mention the volume conf to pick the volume ID based on the ENV credentials if any cluster/volumes.yml

    5. Add the conf to env cluster/conf/dev.yaml | qa.yml | uat.yml | prod.yml | state.yaml

    6. Add ZUUL Routes  cluster/app/egov/gateway/zuul.yml

    7. docker repo creation and provide permission

      1. . Create docker repositories {egovio/<service_name>} and {egovio/<service_name>}-db"

    8. Roll Action:
      https://github.com/egovernments/egov-mdms-data/data/pb/ACCESSCONTROL-ROLEACTIONS/roleactions.json


    9. CI/CD

      Manual steps:
      This script will read application properties from {} and create necessary build/deploy configuration. You may still need to do following things manually.
      1
      2. Create jenkins build job {} under {}".format(args.service, args.project)
      3. Manually look through <service_name>.yml in InfraOps repo and remove unwanted properties.
      It should only contain properties that needs to be overridden.
      ex: db parameters (environment specific), kafka consumer id (can be edited by dev to test from beginning) etc"
      4. You may also want to enable <service_name> in dev/qa environments by adding in respective environment manifests"



  • No labels