fix: migrate JD01 registry to k3s workload
This commit is contained in:
@@ -209,10 +209,33 @@ export interface ControlPlaneNodeSpec {
|
||||
route: string;
|
||||
kubeRoute: string;
|
||||
k3s: ControlPlaneK3sNodeSpec | null;
|
||||
registry: { endpoint: string };
|
||||
registry: ControlPlaneRegistrySpec;
|
||||
egressProxy: ControlPlaneEgressProxySpec | null;
|
||||
}
|
||||
|
||||
export type ControlPlaneRegistrySpec = ControlPlaneHostDockerRegistrySpec | ControlPlaneK8sWorkloadRegistrySpec;
|
||||
|
||||
export interface ControlPlaneHostDockerRegistrySpec {
|
||||
mode: "host-docker";
|
||||
endpoint: string;
|
||||
}
|
||||
|
||||
export interface ControlPlaneK8sWorkloadRegistrySpec {
|
||||
mode: "k8s-workload";
|
||||
endpoint: string;
|
||||
namespace: string;
|
||||
deploymentName: string;
|
||||
serviceName: string;
|
||||
pvcName: string;
|
||||
storage: string;
|
||||
image: string;
|
||||
imagePullPolicy: "Always" | "IfNotPresent" | "Never";
|
||||
containerPort: number;
|
||||
listenHost: string;
|
||||
listenPort: number;
|
||||
hostNetwork: boolean;
|
||||
}
|
||||
|
||||
export interface ControlPlaneK3sNodeSpec {
|
||||
serviceName: string;
|
||||
dropInPath: string;
|
||||
|
||||
Reference in New Issue
Block a user