Oracle International Corporation

Joshua Aaron Horwitz

Andrew James Pryde

Jacob Lindholm

Aseem Bajaj

David Sang-Chul Nahm

Prabhakar Palanivel

Techniques are described herein for authenticating a pod. A method can include a manager instance receiving a first request for a first token to access a computing resource. The manager instance can determine an identity of the service account and generate a second request for the first token based at least in part on the authentication. The manager instance can transmit the second request to a token issuance service of the computing system. The token issuance service can generate a third request for the first token, the third request comprising the identity of the service account and a token issuance service signature. The token issuance service can transmit the third request to an identity service of the computing system. The identity service can generate the first token based at least in part on determining whether to generate the first token.

Workload identity resource principle

A distributed database service can be migrated from a source environment to a destination environment. The distributed database service can be associated with a database and database members. the source environment can include source database members such that each source database member includes a respective image of the database. Migrating the distributed database service can include provisioning a migration gateway in the source environment. Migrating the distributed database service can also include provisioning a domain name system service in the destination environment. Migrating the distributed database service can also include provisioning a first destination database member in the destination environment. While updating the first destination database member with a respective image of the database, the distributed database service can process a database request.

Mechanism for zero downtime migration of strongly consistent distributed database clusters

Systems, devices, and methods discussed herein are directed to modifying aspects of a compute instance. A user may request a change to the compute instance. The system may derive a state object indicating a future state of the compute instance were the change to be applied. A hash of a subset of the state object's attributes may be computed and provided to the requesting computing component. The system may subsequently proceed with applying the change. A current state object indicating a current state of the compute instance may be derived based on applying the change. An additional hash of the subset of the current state object's attributes may be computed and provided to the requesting computing component. The two hashes may be configured to enable the requesting computing component to verify the change to the compute instance has been implemented.

Techniques for modifying a compute instance

Techniques for migrating worker nodes within clusters to a new manager instance. One technique includes receiving a request to migrate or update a configuration of a cluster within a container system, where the migration or update includes switching from a first communication pathway to a second communication pathway between worker nodes and a manager instance; creating a component and associated IP address for the second communication pathway; communicating a pod specification that includes the IP address for the second communication pathway to the manager instance, where the pod specification will cause a container tool to update each of the worker nodes with the IP address for the second communication pathway; receiving a notification that all worker nodes have been updated with the IP address; and removing a component and associated IP address for the first communication pathway from the cluster.

Growing community of inventors

Centreville, VA, United States of America

Joshua Aaron Horwitz