Skip to content

Commit

Permalink
Update known-differences-with-cf-for-vms.md
Browse files Browse the repository at this point in the history
Add section about stack handling to known-differences-with-cf-for-vms.md
  • Loading branch information
FloThinksPi authored and danail-branekov committed Oct 15, 2024
1 parent acbe9f6 commit c20370f
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/known-differences-with-cf-for-vms.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,11 @@ the API shim, the user would only be able to list and view spaces which have rol
### Rolling Updates
In Kofiri `--strategy=rolling` is implemented using k8S rolling update capabilities of the scheduler. At the moment korifi uses statefulsets to run the app workloads. Rolling update for statefulsets stops the old instance before starting the new one, for ordering reasons. If the app has only one instance the udpate will cause a downtime. Apps with more than one instance won't experience any downtime, but they will have one instance less up and running during the update.

### Stack Changes
While in CF for VMs the staging process yields a droplet, which is a stripped container image without base layer/operating system.
In Korifi a fully fledged image is created which includes the base operating system(stack).
This alters the behaviour in case of stack updates. CF for VMs does purposefully combine stack and droplet at container instance creation time - thus a restart of an app consumes a new stack. In Korifi only a restage of an app consumes thew new stack. One might need to detect that and dynamically rebase a droplet onto a new stack in korifi before starting the container to yield the same behaviour here.

## Apps
### App Security Groups

Expand Down

0 comments on commit c20370f

Please sign in to comment.