• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • NONRTRIC Rel-J Dev Sprint #1, NONRTRIC Rel-J Dev Sprint #3

      Current rApp package structure does expect the HELM chart to be available in the target chart repository.

      This should add the helm artifacts as part of the rApp package (Artifacts/Deployment/HELM). Any number of HELM artifacts can be added in a rApp package (size related restrictions still comes into action).

      asd.yaml (Definitions/asd.yaml) should contain the HELM artifact metadata. rApp manager should parse the asd.yaml and use those metadata to find and upload the HELM artifact to the mentioned chart repository(Target repository is per artifact / one per rApp Manager )(Invalid configuration of asd.yaml can make the rApp package invalid??).

      These helm charts should be added to the chart repository mentioned at the rApp create instance time. If the target chart repository isn't available to upload, rApp create instance will fail.

      It is expected that the acm Kubernetes participant should have been configured with the chart repository as part of the setup. rApp manager doesn't handle the whitelisting of the chart repository with Kubernetes participant.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            aravind.est Aravindhan Ayyanathan
            aravind.est Aravindhan Ayyanathan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: