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

Create staging playground deploy workflow and other updates #11079

Merged
merged 11 commits into from
Jun 3, 2024

Conversation

cpepper96
Copy link
Member

Notes for Reviewers

This PR fixes #11042

  • Create workflow for updating the meshery helm release in the staging playground. Added this to the edge release workflow
  • Updated the playground reset job to use secrets.METAL_SERVER1
  • Use pinned version of actions/checkout@v4 in the edge release workflow

Signed commits

  • Yes, I signed my commits.

Signed-off-by: Jerod Culpepper <cpepper96@gmail.com>
Signed-off-by: Jerod Culpepper <cpepper96@gmail.com>
Signed-off-by: Jerod Culpepper <cpepper96@gmail.com>
Signed-off-by: Jerod Culpepper <cpepper96@gmail.com>
Signed-off-by: Jerod Culpepper <cpepper96@gmail.com>
Signed-off-by: Jerod Culpepper <cpepper96@gmail.com>
@github-actions github-actions bot added the area/ci Continuous Integration label Jun 1, 2024
@cpepper96 cpepper96 requested a review from MUzairS15 June 1, 2024 05:47
Copy link

github-actions bot commented Jun 1, 2024

Signed-off-by: Jerod Culpepper <cpepper96@gmail.com>
host: ${{ secrets.METAL_SERVER3 }}
username: root
key: ${{ secrets.METAL_SSH_KEY }}
script: |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be great if we're able to use mesheryctl system update.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a requirement, but ideal to reuse Meshery's tooling.

Copy link
Contributor

@MUzairS15 MUzairS15 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, using mesheryctl will be ideal and we should start doing that.
It also aligns with the ongoing effort of using Meshery to also provision its remote provider instead of helm.

It also helps identifies where is the pain point or bugs in the flow.
Eventually, we should use mesheryctl for deploying in prod as well.

Signed-off-by: Jerod Culpepper <cpepper96@gmail.com>
@cpepper96
Copy link
Member Author

Updated to use mesheryctl @leecalcote @MUzairS15

@leecalcote
Copy link
Member

Good deal. I think that this command is all that we need. We'll find out shortly. 😉

@leecalcote leecalcote merged commit 7c92f1a into meshery:master Jun 3, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci Continuous Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI] Continuous Delivery setup to staging-playground.meshery.io
3 participants