2024-10-17 Technical Sync Meeting

[github-actions[bot]]

Meeting notices

Antitrust Policy

The Steering Members, General Members, and Contributors acknowledge that they may compete with one another in various lines of business and that it is therefore imperative that they and their respective representatives act in a manner that does not violate any applicable antitrust laws and regulations. Each Steering Member, General Member, and Contributor may have similar agreements with others. Each Steering Member, General Member, and Contributor may design, develop, manufacture, acquire or market competitive deliverables, products and services, and conduct its business, in whatever way it chooses. No Steering Member, General Member, or Contributor is obligated to announce or market any products or services associated with or based on the Project. Without limiting the generality of the foregoing, the Steering Members, General Members, and Contributors agree not to have any discussion relating to any product pricing, methods or channels of product distribution, division of markets, allocation of customers or any other topic that should not be discussed among competitors.

Reminder - Meeting is recorded

• Chair: Armand Craig (Rockwell) - @ajcraig
• Project Management: Jory Burson (Linux Foundation) - @jorydotcom

Agenda

• [ ] Convene & Welcome New Participants
• [ ] Review Agenda
• [ ] Review Proposed release 1 scope (move to Github / establish timeline for FB and approval process)
• [ ] Review open PRs
• [ ] Open discussion

Review Project Board

• [ ] Add work items to review or discuss from the project board/roadmap

Review PRs

• [ ] PR splitting the application observability content up across the different sections.

Review Issues

• [ ] Add issues that need review, assignment, triage, or other clarification

AOB

• [ ] Add any other items that were raised for discussion

Items for next meeting

• [ ] Add any items that should be covered in the next meeting

Adjournment

[tomcounihan]

Attended

[phil-abb]

@LiamRandall I watched the recording from today's session and I have a question about what parts of operators fits into Margo's scope.

Are you indicating that Margo should allow application developers to deploy operators as part of their application deployment? Meaning, we'd need to do something to allow for applications to require elevated permissions in order for the operator to be installed and run?

Are you indicating that Margo should define a set of operators that must be included as part of the device's requirement (e.g., the cert-manager operator)?

Or do you mean something else?

I might be misunderstanding what your concerns are because to me whether or not an application developer wants to use an operator is an implementation choice they make and the only thing we'd need to determine for Margo is if allowing app developers to install operators that could potentially access all namespaces or require elevated permissions to deploy and run, is a concern.