Class: Ansible::Ruby::Modules::K8s

Inherits:
Base show all
Defined in:
lib/ansible/ruby/modules/generated/clustering/k8s/k8s.rb,
lib/ansible/ruby/modules/generated/clustering/k8s/k8s_raw.rb,
lib/ansible/ruby/modules/generated/clustering/openshift/openshift_raw.rb

Overview

Use the OpenShift Python client to perform CRUD operations on K8s objects. Pass the object definition from a source file or inline. See examples for reading files and using Jinja templates. Access to the full range of K8s APIs. Use the M(k8s_facts) module to obtain a list of items about an object of type C(kind) Authenticate using either a config file, certificates, password or token. Supports check mode.

Instance Method Summary collapse

Methods inherited from Base

#ansible_name, #to_h

Methods inherited from Ansible::Ruby::Models::Base

attr_option, attr_options, attribute, fix_inclusion, #initialize, remove_existing_validations, #to_h, validates

Constructor Details

This class inherits a constructor from Ansible::Ruby::Models::Base

Instance Method Details

#merge_type ⇒ :json, ...

Returns Whether to override the default patch merge approach with a specific type. By the default, the strategic merge will typically be used.,For example, Custom Resource Definitions typically aren’t updatable by the usual strategic merge. You may want to use C(merge) if you see “strategic merge patch format is not supported”,See U(kubernetes.io/docs/tasks/run-application/update-api-object-kubectl-patch/#use-a-json-merge-patch-to-update-a-deployment),Requires openshift >= 0.6.2,If more than one merge_type is given, the merge_types will be tried in order,If openshift >= 0.6.2, this defaults to C([‘strategic-merge’, ‘merge’]), which is ideal for using the same parameters on resource kinds that combine Custom Resources and built-in resources. For openshift < 0.6.2, the default is simply C(strategic-merge).

Returns:

  • (:json, :merge, :"strategic-merge", nil) —

    Whether to override the default patch merge approach with a specific type. By the default, the strategic merge will typically be used.,For example, Custom Resource Definitions typically aren’t updatable by the usual strategic merge. You may want to use C(merge) if you see “strategic merge patch format is not supported”,See U(kubernetes.io/docs/tasks/run-application/update-api-object-kubectl-patch/#use-a-json-merge-patch-to-update-a-deployment),Requires openshift >= 0.6.2,If more than one merge_type is given, the merge_types will be tried in order,If openshift >= 0.6.2, this defaults to C([‘strategic-merge’, ‘merge’]), which is ideal for using the same parameters on resource kinds that combine Custom Resources and built-in resources. For openshift < 0.6.2, the default is simply C(strategic-merge).



17
 
# File 'lib/ansible/ruby/modules/generated/clustering/k8s/k8s.rb', line 17

attribute :merge_type