google-apis-container_v1beta1 0.9.0 → 0.10.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 928cb84d4871fe5b791be84e692de93befd901897ba7009228080e0dacb14a0c
-  data.tar.gz: 4b37ee1dbfedc5b980884679196e37402e6260059353adc34a0702330e30f9ca
+  metadata.gz: b2e0d342010734d2714295a5d4101f133724802c1898be6bd5333f473d62533b
+  data.tar.gz: 8d772ed02127d0e7aa2a830fa7de8a5c37a02b64b937b4d92324047fb7bd35ae
 SHA512:
-  metadata.gz: 3eeeb0caffcf5b8e1f893e548168f2440e30c2cf9d25f236bf1191ffcb84f6cae4d1cea9891183c6a57f3e383d313084019793270dedc0d6e302a4afc9956f70
-  data.tar.gz: 132da4b04076fb8f10b78bc71923b51295024a1fe9c6bf7d7d6afcbf1d2993533ace5b25cff6354335251948a127f9eb51d7f4456a915feb2a5f2fee712dfa8d
+  metadata.gz: eb58a482a9f2863c3da99c6092328378d7b8a74570c9176f989586440d6fe70c56d67502608adf3aec69a621df4246a284d9f01f2de36e501ccfc7cfa1f693a5
+  data.tar.gz: ed5ca71eb0f26edcc0e738259f9d78543a293ef7929619442a17b016a0cef037baec051b1ba9fd787928dc8f0539e87461b7454dad23248db797f5abc6c10076

data/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Release history for google-apis-container_v1beta1
 
+### v0.10.0 (2021-06-03)
+
+* Regenerated from discovery document revision 20210521
+* Regenerated using generator version 0.3.0
+
 ### v0.9.0 (2021-05-26)
 
 * Regenerated from discovery document revision 20210517

data/lib/google/apis/container_v1beta1/classes.rb

@@ -238,6 +238,11 @@ module Google
         # @return [String]
         attr_accessor :disk_type
       
+        # The image type to use for NAP created node.
+        # Corresponds to the JSON property `imageType`
+        # @return [String]
+        attr_accessor :image_type
+      
         # NodeManagement defines the set of node management services turned on for the
         # node pool.
         # Corresponds to the JSON property `management`
@@ -280,20 +285,7 @@ module Google
         # @return [Google::Apis::ContainerV1beta1::ShieldedInstanceConfig]
         attr_accessor :shielded_instance_config
       
-        # These upgrade settings control the level of parallelism and the level of
-        # disruption caused by an upgrade. maxUnavailable controls the number of nodes
-        # that can be simultaneously unavailable. maxSurge controls the number of
-        # additional nodes that can be added to the node pool temporarily for the time
-        # of the upgrade to increase the number of available nodes. (maxUnavailable +
-        # maxSurge) determines the level of parallelism (how many nodes are being
-        # upgraded at the same time). Note: upgrades inevitably introduce some
-        # disruption since workloads need to be moved from old nodes to new, upgraded
-        # ones. Even if maxUnavailable=0, this holds true. (Disruption stays within the
-        # limits of PodDisruptionBudget, if it is configured.) Consider a hypothetical
-        # node pool with 5 nodes having maxSurge=2, maxUnavailable=1. This means the
-        # upgrade process upgrades 3 nodes simultaneously. It creates 2 additional (
-        # upgraded) nodes, then it brings down 3 old (not yet upgraded) nodes at the
-        # same time. This ensures that there are always at least 4 nodes available.
+        # Upgrade settings control disruption and speed of the upgrade.
         # Corresponds to the JSON property `upgradeSettings`
         # @return [Google::Apis::ContainerV1beta1::UpgradeSettings]
         attr_accessor :upgrade_settings
@@ -307,6 +299,7 @@ module Google
           @boot_disk_kms_key = args[:boot_disk_kms_key] if args.key?(:boot_disk_kms_key)
           @disk_size_gb = args[:disk_size_gb] if args.key?(:disk_size_gb)
           @disk_type = args[:disk_type] if args.key?(:disk_type)
+          @image_type = args[:image_type] if args.key?(:image_type)
           @management = args[:management] if args.key?(:management)
           @min_cpu_platform = args[:min_cpu_platform] if args.key?(:min_cpu_platform)
           @oauth_scopes = args[:oauth_scopes] if args.key?(:oauth_scopes)
@@ -1468,7 +1461,20 @@ module Google
         # specification, under the control of the cluster master. They may have a set of
         # Kubernetes labels applied to them, which may be used to reference them during
         # pod scheduling. They may also be resized up or down, to accommodate the
-        # workload.
+        # workload. These upgrade settings control the level of parallelism and the
+        # level of disruption caused by an upgrade. maxUnavailable controls the number
+        # of nodes that can be simultaneously unavailable. maxSurge controls the number
+        # of additional nodes that can be added to the node pool temporarily for the
+        # time of the upgrade to increase the number of available nodes. (maxUnavailable
+        # + maxSurge) determines the level of parallelism (how many nodes are being
+        # upgraded at the same time). Note: upgrades inevitably introduce some
+        # disruption since workloads need to be moved from old nodes to new, upgraded
+        # ones. Even if maxUnavailable=0, this holds true. (Disruption stays within the
+        # limits of PodDisruptionBudget, if it is configured.) Consider a hypothetical
+        # node pool with 5 nodes having maxSurge=2, maxUnavailable=1. This means the
+        # upgrade process upgrades 3 nodes simultaneously. It creates 2 additional (
+        # upgraded) nodes, then it brings down 3 old (not yet upgraded) nodes at the
+        # same time. This ensures that there are always at least 4 nodes available.
         # Corresponds to the JSON property `nodePool`
         # @return [Google::Apis::ContainerV1beta1::NodePool]
         attr_accessor :node_pool
@@ -3168,7 +3174,20 @@ module Google
       # specification, under the control of the cluster master. They may have a set of
       # Kubernetes labels applied to them, which may be used to reference them during
       # pod scheduling. They may also be resized up or down, to accommodate the
-      # workload.
+      # workload. These upgrade settings control the level of parallelism and the
+      # level of disruption caused by an upgrade. maxUnavailable controls the number
+      # of nodes that can be simultaneously unavailable. maxSurge controls the number
+      # of additional nodes that can be added to the node pool temporarily for the
+      # time of the upgrade to increase the number of available nodes. (maxUnavailable
+      # + maxSurge) determines the level of parallelism (how many nodes are being
+      # upgraded at the same time). Note: upgrades inevitably introduce some
+      # disruption since workloads need to be moved from old nodes to new, upgraded
+      # ones. Even if maxUnavailable=0, this holds true. (Disruption stays within the
+      # limits of PodDisruptionBudget, if it is configured.) Consider a hypothetical
+      # node pool with 5 nodes having maxSurge=2, maxUnavailable=1. This means the
+      # upgrade process upgrades 3 nodes simultaneously. It creates 2 additional (
+      # upgraded) nodes, then it brings down 3 old (not yet upgraded) nodes at the
+      # same time. This ensures that there are always at least 4 nodes available.
       class NodePool
         include Google::Apis::Core::Hashable
       
@@ -3256,20 +3275,7 @@ module Google
         # @return [String]
         attr_accessor :status_message
       
-        # These upgrade settings control the level of parallelism and the level of
-        # disruption caused by an upgrade. maxUnavailable controls the number of nodes
-        # that can be simultaneously unavailable. maxSurge controls the number of
-        # additional nodes that can be added to the node pool temporarily for the time
-        # of the upgrade to increase the number of available nodes. (maxUnavailable +
-        # maxSurge) determines the level of parallelism (how many nodes are being
-        # upgraded at the same time). Note: upgrades inevitably introduce some
-        # disruption since workloads need to be moved from old nodes to new, upgraded
-        # ones. Even if maxUnavailable=0, this holds true. (Disruption stays within the
-        # limits of PodDisruptionBudget, if it is configured.) Consider a hypothetical
-        # node pool with 5 nodes having maxSurge=2, maxUnavailable=1. This means the
-        # upgrade process upgrades 3 nodes simultaneously. It creates 2 additional (
-        # upgraded) nodes, then it brings down 3 old (not yet upgraded) nodes at the
-        # same time. This ensures that there are always at least 4 nodes available.
+        # Upgrade settings control disruption and speed of the upgrade.
         # Corresponds to the JSON property `upgradeSettings`
         # @return [Google::Apis::ContainerV1beta1::UpgradeSettings]
         attr_accessor :upgrade_settings
@@ -5133,20 +5139,7 @@ module Google
         # @return [Google::Apis::ContainerV1beta1::NodeTaints]
         attr_accessor :taints
       
-        # These upgrade settings control the level of parallelism and the level of
-        # disruption caused by an upgrade. maxUnavailable controls the number of nodes
-        # that can be simultaneously unavailable. maxSurge controls the number of
-        # additional nodes that can be added to the node pool temporarily for the time
-        # of the upgrade to increase the number of available nodes. (maxUnavailable +
-        # maxSurge) determines the level of parallelism (how many nodes are being
-        # upgraded at the same time). Note: upgrades inevitably introduce some
-        # disruption since workloads need to be moved from old nodes to new, upgraded
-        # ones. Even if maxUnavailable=0, this holds true. (Disruption stays within the
-        # limits of PodDisruptionBudget, if it is configured.) Consider a hypothetical
-        # node pool with 5 nodes having maxSurge=2, maxUnavailable=1. This means the
-        # upgrade process upgrades 3 nodes simultaneously. It creates 2 additional (
-        # upgraded) nodes, then it brings down 3 old (not yet upgraded) nodes at the
-        # same time. This ensures that there are always at least 4 nodes available.
+        # Upgrade settings control disruption and speed of the upgrade.
         # Corresponds to the JSON property `upgradeSettings`
         # @return [Google::Apis::ContainerV1beta1::UpgradeSettings]
         attr_accessor :upgrade_settings
@@ -5281,20 +5274,7 @@ module Google
         end
       end
       
-      # These upgrade settings control the level of parallelism and the level of
-      # disruption caused by an upgrade. maxUnavailable controls the number of nodes
-      # that can be simultaneously unavailable. maxSurge controls the number of
-      # additional nodes that can be added to the node pool temporarily for the time
-      # of the upgrade to increase the number of available nodes. (maxUnavailable +
-      # maxSurge) determines the level of parallelism (how many nodes are being
-      # upgraded at the same time). Note: upgrades inevitably introduce some
-      # disruption since workloads need to be moved from old nodes to new, upgraded
-      # ones. Even if maxUnavailable=0, this holds true. (Disruption stays within the
-      # limits of PodDisruptionBudget, if it is configured.) Consider a hypothetical
-      # node pool with 5 nodes having maxSurge=2, maxUnavailable=1. This means the
-      # upgrade process upgrades 3 nodes simultaneously. It creates 2 additional (
-      # upgraded) nodes, then it brings down 3 old (not yet upgraded) nodes at the
-      # same time. This ensures that there are always at least 4 nodes available.
+      # 
       class UpgradeSettings
         include Google::Apis::Core::Hashable
       

data/lib/google/apis/container_v1beta1/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module ContainerV1beta1
       # Version of the google-apis-container_v1beta1 gem
-      GEM_VERSION = "0.9.0"
+      GEM_VERSION = "0.10.0"
 
       # Version of the code generator used to generate this client
-      GENERATOR_VERSION = "0.2.0"
+      GENERATOR_VERSION = "0.3.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20210517"
+      REVISION = "20210521"
     end
   end
 end

data/lib/google/apis/container_v1beta1/representations.rb

@@ -824,6 +824,7 @@ module Google
           property :boot_disk_kms_key, as: 'bootDiskKmsKey'
           property :disk_size_gb, as: 'diskSizeGb'
           property :disk_type, as: 'diskType'
+          property :image_type, as: 'imageType'
           property :management, as: 'management', class: Google::Apis::ContainerV1beta1::NodeManagement, decorator: Google::Apis::ContainerV1beta1::NodeManagement::Representation
       
           property :min_cpu_platform, as: 'minCpuPlatform'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-container_v1beta1
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.10.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-05-31 00:00:00.000000000 Z
+date: 2021-06-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-apis-core
@@ -52,7 +52,7 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google-apis-container_v1beta1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-container_v1beta1/v0.9.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-container_v1beta1/v0.10.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google-apis-container_v1beta1
 post_install_message: 
 rdoc_options: []