Fortify - set required labels for kiali
General MR
Summary
-
Epic work which adds Kiali
app
andversion
required labels to Fortify for telemetry capture. - Updated templating in
webapp.yaml
to addtpl
for label interpretation. - Added
app
andversion
podLabels in values.yaml under mysql.primary.podLabels.
Relevant logs/screenshots
Validated labels are now properly populated in Kiali for Fortify pods:
Linked Issue
Upgrade Notices
N/A
Edited by Luis Gomez
Merge request reports
Activity
changed milestone to %2.36.0
added fortify priority6 statusdoing teamService Mesh labels
assigned to @lgomez2
added 3 commits
-
8cd7c197...b7f54bf3 - 2 commits from branch
main
- 7fdc2498 - Merge branch 'main' of https://repo1.dso.mil/big-bang/product/packages/fortify...
-
8cd7c197...b7f54bf3 - 2 commits from branch
added 1 commit
- c2b95e6f - Added in puts to CHANGELOG.md and updated version tag in chart/Chart.yaml to 1.1.2320154-bb.19
added 1 commit
- ad3f4f92 - Added inputs to docs/DEVELOPMENT_MAINTENANCE.md for msql podLabels addition to values.yaml
added 1 commit
- 97ea4549 - Minor tweak to README.md changed dashes to astrix to satisfy MD file lint checks.
To test the labels in a k3d cluster:
- Deploy a k3d cluster
- Checkout the BB test branch:
fortify-130-set-required-labels-for-kiali
. The branch has the BB umbrella templating required to validate kiali labels: templating - Deploy Big Bang. Make sure you have fortify and Kiali enabled and pointed to the correct branch in your overrides:
144-set-required-labels-for-kiali
Example snippet:
jaeger: enabled: true monitoring: enabled: false grafana: enabled: false kiali: enabled: true values: cr: spec: auth: strategy: "openid" addons: authservice: enabled: true fortify: enabled: true sourceType: "git" git: repo: "https://repo1.dso.mil/big-bang/product/packages/fortify.git" path: "chart" tag: null branch: "130-set-required-labels-for-kiali" values: trust_store_password: dsoppassword key_store_password: dsoppassword key_store_cert_password : dsoppassword
- Navigate to Kiali (https://kiali.dev.bigbang.mil/)
- In main menu, choose
Workloads
, If you see "no namespace is selected" here you may need to select the fortify namespace in theSelect Namespaces
drop-down menu). Validate thatapp
andversion
labels are populated for pods in the namespace.
requested review from @dpritchettrm, @matt.vasquez, @nbazzeghin, @cschaefer, @alfredodiaz53, and @daniel.stocum
removed statusdoing label
added statusreview label
mentioned in commit 4901508f
Please register or sign in to reply