Resolve "Fix Fortify PIpeline"
Package Merge Request
Package Changes
BB pipelines were failing due to Fortify deploy and tests failing. Fortify was not initially working via Istio for 2 reasons:
- Fortify was only responding on 8443 port at the pod. Fortify was not accepting requests on 8080. We needed Istio VS routing to the HTTP port
- NetworkPolicy was not working correctly allowing ingress from Istio to Fortify
This MR should update the Fortify Chart to the tag with updates needed to fix tests and istio access as well as set the Cypress test URL for fortify.
Package MR
big-bang/product/packages/fortify!70 (merged)
For Issue
Closes #1722 (closed)
Edited by Jared Ladner
Merge request reports
Activity
added statusreview label
added fortify label
added debug label
added statusdoing label and removed statusreview label
@jaredmladner does this need
SKIP UPGRADE
to not run the upgrade stage?added 9 commits
-
6f868efc...d640df13 - 8 commits from branch
master
- c74bfd36 - Merge branch 'master' into 1722-fix-fortify-pipeline
-
6f868efc...d640df13 - 8 commits from branch
added 17 commits
- 5748b0d1...726673bd - 7 earlier commits
- c55e256c - gitlab update to 7.3.1-bb.0
- 06fff339 - velero update to 4.0.3-bb.1
- da3c0968 - fix k3d-dev.sh SUBNET_ID specifier and public ip
- a273055a - fix: ips conditionals for logging
- 797cd1c9 - docs: fix typo in authservice docs
- 4ba38d22 - velero update to 5.0.2-bb.1
- e486ae0e - SKIP UPGRADE Revert "Merge branch 'update-loki-tag-5.21.0-bb.0' into 'master'"
- cebbc482 - keycloak update to 18.4.3-bb.5
- df945e56 - gitlab update to 7.3.1-bb.1
- 5c0cd600 - reverting
Toggle commit listadded 33 commits
-
1811fe52...d38746d5 - 32 commits from branch
master
- 9f74c370 - Merge branch 'master' into 1722-fix-fortify-pipeline
-
1811fe52...d38746d5 - 32 commits from branch
added 17 commits
-
9f74c370...6b746326 - 16 commits from branch
master
- 1c67b4f9 - mergin master
-
9f74c370...6b746326 - 16 commits from branch
Please register or sign in to reply