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

feat(deploy): split Deployments #1009

Open
wants to merge 15 commits into
base: main
Choose a base branch
from
Open

feat(deploy): split Deployments #1009

wants to merge 15 commits into from

Conversation

andrewazores
Copy link
Member

@andrewazores andrewazores commented Jan 14, 2025

Welcome to Cryostat! 👋

Before contributing, make sure you have:

  • Read the contributing guidelines
  • Linked a relevant issue which this PR resolves
  • Linked any other relevant issues, PR's, or documentation, if any
  • Resolved all conflicts, if any
  • Rebased your branch PR on top of the latest upstream main branch
  • Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
  • Signed all commits: git commit -S -m "YOUR_COMMIT_MESSAGE"

Fixes: #814
Includes:

Description of the change:

This change adds allows the users to provide...

Motivation for the change:

This change is helpful because users may want to...

How to manually test:

  1. Insert steps here...
  2. ...

@mergify mergify bot added the safe-to-test label Jan 14, 2025
@andrewazores andrewazores added the feat New feature or request label Jan 14, 2025
@andrewazores andrewazores marked this pull request as draft January 14, 2025 21:34
@andrewazores
Copy link
Member Author

/build_test

Copy link

/build_test completed successfully ✅.
View Actions Run.

@andrewazores andrewazores marked this pull request as ready for review January 24, 2025 20:53
@andrewazores
Copy link
Member Author

@ebaron unless you think #1024 is worth getting done (I think it's fine to hold until later, and then we can also implement CRD API for the URI range controls) then this should be ready to go. It's just a roll-up of the PRs listed in the PR body, which were all getting resynced with this and main as things went on, so this should be identical to the split-pvcs PR that went in last.

@ebaron
Copy link
Member

ebaron commented Jan 24, 2025

@ebaron unless you think #1024 is worth getting done (I think it's fine to hold until later, and then we can also implement CRD API for the URI range controls) then this should be ready to go. It's just a roll-up of the PRs listed in the PR body, which were all getting resynced with this and main as things went on, so this should be identical to the split-pvcs PR that went in last.

I vote for holding off on #1024 for 4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request safe-to-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Story] Deploy database and storage containers separately
3 participants