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.

Sign up for GitHub

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

Jump to bottom

POC: verify the idea to use a separate state for setting billable/non-billable information in RuntimeCR #636

Open
1 task
tobiscr opened this issue Jan 30, 2025 · 0 comments
Open
1 task

POC: verify the idea to use a separate state for setting billable/non-billable information in RuntimeCR #636

tobiscr opened this issue Jan 30, 2025 · 0 comments
Labels
area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature.

Comments

@tobiscr
Copy link
Contributor

tobiscr commented Jan 30, 2025

Description

Create a POC to check which options we have to set the billable field in RuntimeCR.

Ideas: use a dedicated state which sets the billable field before we set the status-field to READY.

Verify that we don't end up with an ObjectModified error case during reconciliation.

AC:

  • Identify the best way for setting the billable field in FSM

Reasons

Clarify technical options.

Attachments
@tobiscr tobiscr added area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature. labels Jan 30, 2025
@tobiscr tobiscr changed the title POC: verify the ideal to use a separate state for setting billable/non-billable information in RuntimeCR POC: verify the idea to use a separate state for setting billable/non-billable information in RuntimeCR Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tobiscr