Versions Compared

Old Version 3

changes.mady.by.user Pawel Pawlak

Saved on

compared with

New Version Current

changes.mady.by.user Pawel Pawlak

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira No
SummaryDescriptionStatusSolution

Request from the Policy project group (Ramesh and Liam) 

‘cluster-admin’ permission on one of their helm charts in OOM for automate helm chart installation for microservice. 

View file
namek8s-ppnt-cluster-role requirements.pptx
height150

Requested change in the OOM repository by defining a cluster role binding for the K8s participant (provided by CLAMP repository) in its HELM chart which allows the component to create/update/delete resources on the cluster scope.

K8s participant should have a mechanism that would validate HELM chart before deploying it. Those would be signatures, hashed or signed HELM chart. Service mesh in Jakarta could take part of securing access.

ongoingNeed to have a mechanism to validate the HELM chart and repository from which fetching the HELM chart from.

SECCOM presentations for incoming DDF (January).

Deadline for submission: December 3rd: 

  • SECCOM topics backlog for DDF (4 bullets we merge into one presentation: use cases, GRs and BPs):
    • Logging requirements clarification – Bob (why, rationale, requirement),/Byung (how, architecture and design perspective) - https://wiki.lfnetworking.org/display/LN/2022-01-DD+-+ONAP%3A+Security+and+Logging - flow matrix importance for authentication between components
    • New requirements for Jakarta – Amy/Pawel – all in one – GR review with David
    • Recommended versions (SECCOM and OOM) – Amy/Pawel/Sylvain
    • Packages upgrades - Jakarta update - Amy/Pawel
    • Unmaintained code handling and its impact on documentation (SECCOM + Documentation) - main session stream Amy/Pawel/Thomas/Eric
    • Code quality demo - main session stream - Fabian/Kevin
  • Interproject proposals:
    • SBOMs ONAP story – Muddasar/Pawel
ongoingProposals to be reviewed next SECCOM (last minute)

Fabian to share by e-mail his insight on flow matrix.

Fabian to check with Kevin/Thierry if by DDF we could provide demo.


TSC voting process for submitted requirementsDeadline is on 2nd of December.ongoingNo action required on our side.

OUR NEXT SECCOM MEETING CALL WILL BE HELD ON 30th 4th OF NOVEMBERDECEMBER'21. 

Part 1

SECCOM proposal for DDF:

  • Logging requiremets clarification
  • New requirements for Jakarta
  • Recommended versions (SECCOM and OOM)
  • Packages upgrades - Jakarta update
  • Umnaintained code handling and its impact on documentation (SECCOM + Documentation) - main session stream
  • Code quality demo - main session stream

Interproject proposals:

  • SBOMs ONAP story

SECCOM MEETING CALL WILL BE HELD ON 30th OF NOVEMBER'21. 

Part 2

Request from the Policy project group (Ramesh and Liam) for the ‘cluster-admin’ permission on one of their helm charts in OOM for automate helm chart installation for microservice. Quality gates for code quality improvements.


Recording: 

View file
name2021-11-30_SECCOM_week.mp4
height150


SECCOM presentation:


View file
name2021-11-30 ONAP Security Meeting - AgendaAndMinutes.pptx
height150