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
We need to create a new fuel-core Github Action workflow that will remotely trigger a new fuel-deployment Github Action workflow to create an ephemeral test workflow environment/namespace inside the DEV EKS cluster - this will work off the logic @ellioty has built for remote trigger.
Criteria to create ephemeral workflow environment:
If we a developer creates a remote branch (anything but master) we will give the manual option for them deploy a ephemeral workflow environment/namespace to DEV EKS Cluster
From the new fuel core workflow, it clones the developer branch and it builds a docker image per the developer branch and then remotely triggers a new fuel-deployment to:
-> create k8s namespace : it should be named like "fuel-" following the developer branch name
-> deploy the fuel-core helm chart with the built docker image sha per developer branch
Overview:
Criteria to create ephemeral workflow environment:
There is a possibility of them passing custom ENV overrides, but for most part we should mimic fueldevsway.env- https://github.com/FuelLabs/fuel-deployment/blob/master/config/eks/fuel-dev1/fueldevsway.env
What the workflow does:
From the new fuel core workflow, it clones the developer branch and it builds a docker image per the developer branch and then remotely triggers a new fuel-deployment to:
-> create k8s namespace : it should be named like "fuel-" following the developer branch name
-> deploy the fuel-core helm chart with the built docker image sha per developer branch
This fuel-core workflow should pass the image sha built during docker build step in fuel-core github actions to a new version/copy of the fuel-deployment "deploy k8s fuel-core" workflow -> https://github.com/FuelLabs/fuel-deployment/blob/master/.github/workflows/deploy-k8s-fuel-core.yml
-> deploy the fuel-core ingress and certificate per "fuel-.swayswap.io'
ENV to use:
We can assume we use a ENV baseline of fueldevsway.env
https://github.com/FuelLabs/fuel-deployment/blob/master/config/eks/fuel-dev1/fueldevsway.env
with the variables being passed and updated by the fuel-core workflow to fuel-deployment workflow as follows
--> k8s-namespace
--> fuel_core_image_tag
--> fuel_core_deployment_version
--> fuel_core_ingress_dns
--> fuel_core_ingress_secret
We can possibly allow developers to override additional parameters if need be.
The text was updated successfully, but these errors were encountered: