Today we continue discussing the best practice from storage engineering:
667) The type of features from the operator sdk used by the product depend on the automation within the container-specific operator specified by the product. If the product wants to restrict its usage of the container, it can take advantage of just the minimum.
668) One of these features is metering and it works the same way as in the public cloud. Containers are still catching up with the public cloud on this feature.
669) The operators can be written in a variety of languages depending on the sdk however in many cases a barebone application without heavy interpreters or compilers is preferred. Go language is used for these purposes and particularly in devOps.
670) There is no special requirement for performance or security from the containerization framework than what the application wants from the host because this is internal and not visible to the user.
671) Operators like update involve scaling down the nodes, then performing the update and then scaling back up. There is no restriction to reuse logic between operators.
672) Operators generally work one at a time on the same cluster. This prevents states from being mixed and allowing each reconcile between state and deploy to happen sequentially.
673) Operators do not have retain any information between invocations. Anything that needs to be persisted has to be part of state.
674) There is no limit to the number of operators run during deploy. It is preferred to run them sequentially one after the other. The more granular the operators the better they are for maintenance.
675) The diagnosability of operators improves with each operator being small and transparent.
667) The type of features from the operator sdk used by the product depend on the automation within the container-specific operator specified by the product. If the product wants to restrict its usage of the container, it can take advantage of just the minimum.
668) One of these features is metering and it works the same way as in the public cloud. Containers are still catching up with the public cloud on this feature.
669) The operators can be written in a variety of languages depending on the sdk however in many cases a barebone application without heavy interpreters or compilers is preferred. Go language is used for these purposes and particularly in devOps.
670) There is no special requirement for performance or security from the containerization framework than what the application wants from the host because this is internal and not visible to the user.
671) Operators like update involve scaling down the nodes, then performing the update and then scaling back up. There is no restriction to reuse logic between operators.
672) Operators generally work one at a time on the same cluster. This prevents states from being mixed and allowing each reconcile between state and deploy to happen sequentially.
673) Operators do not have retain any information between invocations. Anything that needs to be persisted has to be part of state.
674) There is no limit to the number of operators run during deploy. It is preferred to run them sequentially one after the other. The more granular the operators the better they are for maintenance.
675) The diagnosability of operators improves with each operator being small and transparent.
No comments:
Post a Comment