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

Model: AppConfiguration model supports Job resource #374

Closed
ffforest opened this issue Jul 11, 2023 · 0 comments · Fixed by #418 or #439
Closed

Model: AppConfiguration model supports Job resource #374

ffforest opened this issue Jul 11, 2023 · 0 comments · Fixed by #418 or #439
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature
Milestone

Comments

@ffforest
Copy link
Contributor

ffforest commented Jul 11, 2023

What would you like to be added?

Support native Job resource in AppConfiguration model. This includes:

  • Definition of front-end (customer-facing) model
  • Upgrade the corresponding back-end render logic
  • Documentation updated to reflect the new front-end (customer-facing) model: How to use the new model, with all the fields and possible values

Why is this needed?

This is part of the upgrade to AppConfiguration model. This enables kusion to render a Kubernetes job based on user input and supports the transition from the current Server model to AppConfiguration model

Acceptance Criteria

Kusion can properly produce a valid, rendered YAML containing a job, based on the user input from the workload section in the AppConfiguration model.
Documentations updated on Kusionstack.io.

@ffforest ffforest added the kind/feature Categorizes issue or PR as related to a new feature label Jul 11, 2023
@ffforest ffforest added this to the 0.9.0 milestone Jul 11, 2023
This was linked to pull requests Jul 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants