Versions Compared

Key

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

Agenda

Antitrust Policy

Minutes

Action Items

  • See SIG 1 minutes for update on this topic 2025-01-27

Topic 1

  • Comments

Action items

 

R4 Items

  • Will the outstanding items be buildable and testable in R4 by 14th February?

  • UI Improvements is OK

Cluster Creation

  • The code is not that large and not that different to what’s there now

  • The image will be pushed manually

  • The code will be in the code base and will build by the R4 release date

  • The code will be documented

  • Items for R5

    • CI and integration testing will be after R4

    • The image pushing will be done after R4

    • End to end testing will be after R4

Workload Identity

  • Same level of readiness as in cluster creation

  • The image will be pushed manually

  • The code will be in the code base and will build by the R4 release date

  • The code will be documented

Flux support

  • Flux controllers in catalog

  • Flux controllers are being deployed in the sandbox

  • Flux rejects some deployments that work OK in configsync, Fiachra Corcoran is creating a kpt function to solve this issue

  • Documentation will be done

Location of operator code

Discussion on Function Runners in Porch

  • Istvan Kispal presented how KPT functions are run in Porch

  • Isti proposes to also have the executable runtime in the Porch API server as well as the function runner

Action items

  •  Liam Fallon to contact Prashant Mishra to get status on and help with the SPIFFE item
  •  We should probably at some points defines what make a release a release. At the end we are always trying to cover the timeline but at the end in a regular product dev you would not get approved
  •  Write an issue to capture that we should have the O2 IMS operator code integrated into the overall project makefile structure
  •  Capture the proposal from moving the Executable Runtime to the Porch API Server Istvan Kispal