[JBoss JIRA] (SWSQE-605) Establish Central CI Jenkins Master For Kiali
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-605?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-605:
------------------------------------------
Labels: infrastructure (was: )
> Establish Central CI Jenkins Master For Kiali
> ---------------------------------------------
>
> Key: SWSQE-605
> URL: https://issues.jboss.org/browse/SWSQE-605
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
> Priority: Major
> Labels: infrastructure
>
> Our team at one time was allocated a Central CI Jenkins Master.
> Therefore, one of the following,
> Either:
> a) Confirm that our team's Central CI Jenkins Master is still available and usable
> Or
> b) Establish a new Central CI Jenkins Master
> We also need to confirm that Jenkins master in Central Ci will fit our needs like:
> * is it possible to run smee.io client there to consume github events
> * is it possible to install plugins we are using
> * check SLA
> * check backups, upgrades
> * do we want to share it with istio qe team?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (SWSQE-534) Kiali Test Mesh Operator
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-534?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-534:
------------------------------------------
Labels: infrastructure (was: )
> Kiali Test Mesh Operator
> ------------------------
>
> Key: SWSQE-534
> URL: https://issues.jboss.org/browse/SWSQE-534
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
> Labels: infrastructure
>
> Today, we do have some common situations concerning the meshes that we use to test istio and kiali
> 1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline
> 2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command.
> 4) Maistra supported way to injection of the sidecar is the automatic injection and the present pipeline doesn't have this support
> 3) We are going to move to Central CI Jenkins on future so it might be complicated to configure the slaves specific.
> Since the new way to deploy cloud native applications on Kubernetes is the operators (https://github.com/operator-framework/operator-sdk) which encapsulate everything on the operator container (including the ansible flavor), it will simplify the pipeline.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months