Abstract: An example method of managing a custom resource in a container orchestration (CO) system, the CO system including a plurality of hosts executing a controller and a set of workers, is described. The method includes generating, at the controller in response to a specification of the custom resource by a user, a flow plan, the flow plan including a sequence of flows for execution by a worker in the set of workers; providing, by the controller, the flow plan to the worker; executing, by a flow executor on the worker, the sequence of flows in the flow plan to deploy the custom resource; generating, by the flow executor on the worker, at least one event during execution of the flow plan; and notifying, by the worker, the controller of the at least one event.

Abstract: An example method of managing events in a container orchestration (CO) system includes: receiving, at an event processor, a stream of events generated by the CO system, the events generated by worker nodes, control plane nodes, or both of the CO system; tracking, by the event processor, a rate of a plurality of the events in the stream received over a time period; indicating, by the event processor, that each of the plurality of events is non-skippable; determining, by the event processor for a first event in the stream of events after the plurality of events, that the rate exceeds a threshold limit over the time period; indicating, by the event processor, that the first event is skippable; and providing, by the event processor, each event in the stream of events indicated as being non-skippable to software for presentation to a user.

Abstract: An example method of managing a custom resource in a container orchestration (CO) system includes: receiving, from a manager at a management cluster of the CO system, an intent identifier, the management cluster including a controller configured to manage the custom resource, the management cluster storing the intent identifier in a database; receiving, from the manager at the management cluster, a request that updates state of the custom resource; determining, at the management cluster, a match between an intent identifier in the request and the intent identifier stored in the database; and executing, by the controller of the management cluster, a management process for the custom resource in the CO system in response to the match and the request.

Abstract: One or more embodiments provide techniques for migrating a virtual machine (VM) from a private data center to a cloud data center. A hybridity manager receives a request at the cloud data center to replicate a VM from the private data center on the cloud data center. The hybridity manager identifies a source network associated with the VM. The hybridity manager identifies whether there exists a stretched network associated with the source network of the VM. Responsive to determining that there is a stretched network associated with the source network of the VM, the hybridity manager replicates the VM on the stretched network without reconfiguring internet-protocol (IP) settings of the VM.

Abstract: One or more embodiments provide techniques for migrating virtual machines (VMs) from a private data center to a cloud data center. A hybrid cloud manager determines a scope of migration from the private data center to the cloud data center. The hybrid cloud manager groups each VM included in the scope of migration into one or more clusters. The hybrid cloud manager defines one or more migration phases. Each migration phase comprises a subset of the one or more clusters. The hybrid cloud manager generates a migration schedule based on at least the one or more migration phases. The hybrid cloud manager migrates the VMs from the private data center to the cloud data center in accordance with the migration schedule.

Abstract: One or more embodiments provide techniques for migrating virtual machines (VMs) from a private data center to a cloud data center. A hybrid cloud manager determines a scope of migration from the private data center to the cloud data center. The hybrid cloud manager groups each VM included in the scope of migration into one or more clusters. The hybrid cloud manager defines one or more migration phases. Each migration phase comprises a subset of the one or more clusters. The hybrid cloud manager generates a migration schedule based on at least the one or more migration phases. The hybrid cloud manager migrates the VMs from the private data center to the cloud data center in accordance with the migration schedule.

Abstract: One or more embodiments provide techniques for migrating a virtual machine (VM) from a private data center to a cloud data center. A hybridity manager receives a request at the cloud data center to replicate a VM from the private data center on the cloud data center. The hybridity manager identifies a source network associated with the VM. The hybridity manager identifies whether there exists a stretched network associated with the source network of the VM. Responsive to determining that there is a stretched network associated with the source network of the VM, the hybridity manager replicates the VM on the stretched network without reconfiguring internet-protocol (IP) settings of the VM.

Abstract: Consistent with the present disclosure, a block of software code or “software code block” that is executed while particular tests are carried out is assigned a software code block identifier, which is associated with test identifiers, which, in turn, identify the tests that were performed. The software code block identifiers and corresponding test identifiers are then stored in a database. When a portion of the software code block is later modified, either by a change to one or more lines of the code or by deleting or adding code, the corresponding software code block identifier is determined or selected, and then used to access the corresponding test identifiers from the database. The test identifiers are then used to generate a report, for example, that lists each test to be performed in order to determine whether the modified software code block operates properly.

Abstract: Consistent with the present disclosure, a block of software code or “software code block” that is executed while particular tests are carried out is assigned a software code block identifier, which is associated with test identifiers, which, in turn, identify the tests that were performed. The software code block identifiers and corresponding test identifiers are then stored in a database. When a portion of the software code block is later modified, either by a change to one or more lines of the code or by deleting or adding code, the corresponding software code block identifier is determined or selected, and then used to access the corresponding test identifiers from the database. The test identifiers are then used to generate a report, for example, that lists each test to be performed in order to determine whether the modified software code block operates properly.