Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Exposing Nephio APIs consistently to support independent lifecyles #852

Open
efiacor opened this issue Feb 12, 2025 · 0 comments
Open

Exposing Nephio APIs consistently to support independent lifecyles #852

efiacor opened this issue Feb 12, 2025 · 0 comments
Assignees
@radoslawc @ciaranjohnston @gvbalaji @efiacor
Labels
area/api area/modeling area/process-mgmt SIG Release Process Management sig/network-architecture sig/release

Comments

@efiacor
Copy link
Collaborator

efiacor commented Feb 12, 2025

We need to define a mechanism for handling and exposing Nephio APIs consistently so that they can be life-cycled independently of the implementation.

The Nephio apis and CRDs artifacts should ideally be aligned with the codebase/operator/controller that produces it.

A more detailed investigation on how this could be implemented is required.

For a simple update to a CRD, this could potentially be handled via a github action triggered from a change to the downstream artifact.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@radoslawc radoslawc

@ciaranjohnston ciaranjohnston

@gvbalaji gvbalaji

@efiacor efiacor

Labels
area/api area/modeling area/process-mgmt SIG Release Process Management sig/network-architecture sig/release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@radoslawc @ciaranjohnston @gvbalaji @efiacor