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.

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

Build Fuel-Core Workflow to Trigger Fuel-Deployment Create Ephemeral Enviromment Workflow #425

Closed
rfuelsh opened this issue Jun 18, 2022 · 0 comments · Fixed by #506
Closed
Assignees

Comments

@rfuelsh
Copy link
Member

rfuelsh commented Jun 18, 2022

Overview:

  • 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

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.

@rfuelsh rfuelsh moved this from Todo to In Progress in Fuel Network Jun 18, 2022
@rfuelsh rfuelsh changed the title Setup Create k8s Ephemeral Environment Workflow Build Fuel-Core Workflow to Trigger Fuel-Deployment Create Ephemeral Enviromment Workflow Jun 18, 2022
@rfuelsh rfuelsh linked a pull request Jul 26, 2022 that will close this issue
@rfuelsh rfuelsh moved this from In Progress to Review in Fuel Network Jul 31, 2022
@rfuelsh rfuelsh moved this from Review to In Progress in Fuel Network Aug 11, 2022
@rfuelsh rfuelsh moved this from In Progress to Review in Fuel Network Aug 11, 2022
@rfuelsh rfuelsh moved this from Review to In Progress in Fuel Network Aug 11, 2022
@rfuelsh rfuelsh moved this from In Progress to Review in Fuel Network Aug 16, 2022
Repository owner moved this from Review to Done in Fuel Network Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants