Nephio is a Kubernetes-based automation platform for deploying and managing highly distributed, interconnected workloads such as 5G Network Functions, and the underlying infrastructure on which those workloads depend.
Apache License 2.0
104
stars
53
forks
source link
Align deployment functionality between porch, kpt and CS #639
Original issue URL: https://github.com/kptdev/kpt/issues/3255
Original issue user: https://github.com/mortent
Original issue created at: 2022-05-25T16:39:16Z
Original issue last updated at: 2022-05-25T16:39:16Z
Original issue body: We currently have several tools that provide functionality for deploying configuration to a cluster:
Direct deployment of kpt packages with the kpt live cli commands
Deployment through GitOps with Config Sync.
Both tools build on the same underlying tools (https://github.com/kubernetes-sigs/cli-utils) and use a similar approach for storing information about deployed packages in the cluster (ResourceGroup). But they are also sufficiently different that interoperability of the tools isn't great. For example, it is not currently an easy way to transition from applying directly with kpt live to using Config Sync, and the kpt live status command can't easily be used with to check status of a workload deployed through Config Sync and the nomos cli doesn't work with packages deployed with the kpt live commands.
We need to:
Make it easy to move from applying packages with the kpt live cli to doing gitops with Config Sync.
Create a cli experience that works equally well whether a package is applied with kpt live or Config Sync.
Original issue URL: https://github.com/kptdev/kpt/issues/3255 Original issue user: https://github.com/mortent Original issue created at: 2022-05-25T16:39:16Z Original issue last updated at: 2022-05-25T16:39:16Z Original issue body: We currently have several tools that provide functionality for deploying configuration to a cluster:
kpt livecli commandsBoth tools build on the same underlying tools (https://github.com/kubernetes-sigs/cli-utils) and use a similar approach for storing information about deployed packages in the cluster (ResourceGroup). But they are also sufficiently different that interoperability of the tools isn't great. For example, it is not currently an easy way to transition from applying directly with
kpt liveto using Config Sync, and thekpt live statuscommand can't easily be used with to check status of a workload deployed through Config Sync and thenomoscli doesn't work with packages deployed with thekpt livecommands.We need to:
kpt livecli to doing gitops with Config Sync.kpt liveor Config Sync.Original issue comments: