Introduce Preliminary Version of the Guideline Document for Update Propagation #2
Conversation
chirangaalwis
requested review from
DilanUA,
ThilinaManamgoda,
rasanjaya85 and
chamindi-a
update/Propagating_Updates.md
Outdated
| * Updates to configuration files and non-configuration artifacts (e.g. binaries such as, third-party libraries, | ||
| Carbon extensions in the form of OSGi bundles, [Carbon Applications](https://docs.wso2.com/display/Carbon440/Working+with+Carbon+Applications) | ||
| or any security related artifacts such as, Java Keystore files) | ||
| * Integrate changes to the container image source |
There was a problem hiding this comment.
Include changes to the container image source
There was a problem hiding this comment.
@chamindi-a I think we should stick to the verb Integrate here, as Include actually does not imply the meaning, i.e. to perform a change to container image source and deploy it.
Further, this is applicable to the next point which is about installation resources as well.
WDYT?
There was a problem hiding this comment.
@chirangaalwis: I have tried a change as the same verb was used in three instances. if we can change this iam ok
|
@chamindi-a I have updated the PR with the requested changes, as of now. |
update/Propagating_Updates.md
Outdated
| The prime reason for adopting rolling update strategy is its ability to perform an update with zero downtime. | ||
|
|
||
| **Notes:** | ||
| > Apart from the rolling update strategy, we adopt [`OnDelete`](https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#on-delete) |
There was a problem hiding this comment.
@DilanUA @ThilinaManamgoda as per the internal discussion this needs to be changed. Will update this after further testing of the discussed scenario.
chirangaalwis
force-pushed
the
container-guide-update-strategy
branch
from
668e40e to
65de83d
Compare
Purpose
Goals