| commit | 62ccbbb1c7da36bb61174b952c9b5a3f8219e7e7 | [log] [tgz] |
|---|---|---|
| author | rameshiyer27 <ramesh.murugan.iyer@est.tech> | Wed Feb 01 15:06:45 2023 +0000 |
| committer | rameshiyer27 <ramesh.murugan.iyer@est.tech> | Tue Feb 07 09:49:38 2023 +0000 |
| tree | d79f2834b53cc61d8feff2aca811519d25421b16 | |
| parent | 0700486a08b2bc08589f7e6b0be8338d6bbb4efa [diff] |
Fix robot failures in kubernetes CSITs Api, Pap, Clamp configurations are fixed Update Readiness containers as a list entity to wait for more than one component. Issue-ID: POLICY-4546 Signed-off-by: zrrmmua <ramesh.murugan.iyer@est.tech> Change-Id: I8598ddc01905b072edd9eb3030a83d3d806a14eb
Copyright 2018-2019 AT&T Intellectual Property. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode
This source repository contains legacy docker-compose configurations used for CSIT tests, and ONAP Heat instantiations.
Additionally, the policy-base/ and policy-common/ projects are used to generate the OS base for policy images.
Helm directory is added to include the helm chart for policy-models-simulators. To spin the kubernetes pod up:
Running Policy CSIT in kubernetes: To run CSIT in kubernetes, docker/csit/run-k8s-csit.sh script can be invoked with the arguments {install} {project_name} When the project name is not supplied, the script only installs the policy helm charts and doesn't execute any robot tests. To teardown the kubernetes cluster, the same script can be invoked with the argument {uninstall}
Steps involved in running CSIT in kubernetes: