You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2022. It is now read-only.
Currently, Infra components are installed together in the Stack, which can cause problems with #204. We plan to split the installation of Infra components from the current Stack; the Infra installation process is responsible for installing Infra components and the Stack only generates the application framework source code and Deploy repository.
Option 1.
Split the Stack into an Infra Stack and an Application Stack, with the Infra Stack being used exclusively for installing Infra components and making the necessary configurations to dynamically install the necessary Infra components based on the incoming parameters. When executing hln up, the Installation Infra Stack is executed first, followed by the Application Stack (e.g. gin-next), and we first support these Infra components:
Split Stack(include Argocd) to Infra Stack and an Application Stack @vgjm
Infra Stack can run independently, install them by input some env, and record configmap into cluster for Application Stack use it.
update Infra Stack(Prometheus) and enhance Application Stack make them can multiplexing between different applications in the same cluster @92hackers
update Infra Stack(Loki) and enhance Application Stack make them can multiplexing between different applications in the same cluster @92hackers
update Infra Stack(Dapr) and enhance Application Stack make them can multiplexing between different applications in the same cluster @92hackers
update Infra Stack(Nocalhost) and enhance Application Stack make them can multiplexing between different applications in the same cluster @yuyicai
update Infra Stack(Argocd) and enhance Application Stack make them can multiplexing between different applications in the same cluster @yuyicai
update Infra Stack(SealedSecrets) and enhance Application Stack make them can multiplexing between different applications in the same cluster @yuyicai
update Infra Stack(Jeager) and enhance Application Stack make them can multiplexing between different applications in the same cluster @lyzhang1999
update Infra Stack(Istio) and enhance Application Stack make them can multiplexing between different applications in the same cluster @lyzhang1999
hln init && up && down && hln status...... @hongchaodeng
Results.
When hln up is executed, if the Infra component is not installed, it is installed automatically. If it is installed, it is skipped and execute the Application Stack installation.
When a new application is created in the same cluster, the Infra component will remain intact and only application related content will be created, solving the problem of #204.
hln
Enhance hln init command, install infra first, then hln up will run application stack.
The text was updated successfully, but these errors were encountered:
Problem.
Currently, Infra components are installed together in the Stack, which can cause problems with #204. We plan to split the installation of Infra components from the current Stack; the Infra installation process is responsible for installing Infra components and the Stack only generates the application framework source code and Deploy repository.
Option 1.
Split the Stack into an Infra Stack and an Application Stack, with the Infra Stack being used exclusively for installing Infra components and making the necessary configurations to dynamically install the necessary Infra components based on the incoming parameters. When executing hln up, the Installation Infra Stack is executed first, followed by the Application Stack (e.g. gin-next), and we first support these Infra components:
Application Stack
make them can multiplexing between different applications in the same cluster @92hackersApplication Stack
make them can multiplexing between different applications in the same cluster @92hackersApplication Stack
make them can multiplexing between different applications in the same cluster @92hackersApplication Stack
make them can multiplexing between different applications in the same cluster @yuyicaiApplication Stack
make them can multiplexing between different applications in the same cluster @yuyicaiApplication Stack
make them can multiplexing between different applications in the same cluster @yuyicaiApplication Stack
make them can multiplexing between different applications in the same cluster @lyzhang1999Application Stack
make them can multiplexing between different applications in the same cluster @lyzhang1999Results.
When hln up is executed, if the Infra component is not installed, it is installed automatically. If it is installed, it is skipped and execute the Application Stack installation.
When a new application is created in the same cluster, the Infra component will remain intact and only application related content will be created, solving the problem of #204.
hln
Enhance
hln init
command, install infra first, thenhln up
will run application stack.The text was updated successfully, but these errors were encountered: