application definitions use service-level containers #624
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#598 ensure application resilience
fediversity/fediversity
#620 generate kubernetes container from modular service
fediversity/fediversity
#623 applications use modular services
fediversity/fediversity
Reference
fediversity/fediversity#624
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As a Fediversity maintainer,
given that Fediversity applications use modular services (#623),
and we can generate kubernetes containers from modular services (#620),
I want to make our application definitions use such generated Kubernetes containers,
so that we may shift to serving applications at the service level.
make application definitions use generated kubernetes containersto application definitions use service-level containersclosing as out of scope for MVP