Skip to content
This repository has been archived by the owner on Nov 12, 2024. It is now read-only.

Commit

Permalink
Merge pull request #20 from influxdata/genehynson/update-manifests
Browse files Browse the repository at this point in the history 
chore: update manifests
  • Loading branch information
Gene Hynson authored Mar 5, 2022
2 parents 645b768 + e3b7561 commit 27195db
Show file tree
Hide file tree
Showing 2 changed files with 1,888 additions and 101 deletions.
94 changes: 67 additions & 27 deletions config/crd/bases/nifi.orange.com_nificlusters.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3406,10 +3406,8 @@ spec:
type: object
type: object
removeFlowFileOnStartup:
description: removeFlowFileOnStartup specifies if flow.xml.gz should
be deleted on startup. If set to true, each time the NiFi node's pod
is started, the flow.xml.gz file will be deleted. If set to false,
it will not be deleted. Defaults to 'true'.
description: RemoveFlowFileOnStartup specifies if flow.xml.gz should
be removed on startup
type: boolean
rootProcessGroupId:
description: rootProcessGroupId contains the uuid of the root process
Expand Down Expand Up @@ -5029,14 +5027,14 @@ spec:
type: object
ephemeral:
description: "Ephemeral represents a volume that is handled
by a cluster storage driver (Alpha feature). The volume's
lifecycle is tied to the pod that defines it - it will be
created before the pod starts, and deleted when the pod is
removed. \n Use this if: a) the volume is only needed while
the pod runs, b) features of normal volumes like restoring
from snapshot or capacity tracking are needed, c) the storage
driver is specified through a storage class, and d) the storage
driver supports dynamic volume provisioning through a PersistentVolumeClaim
by a cluster storage driver. The volume's lifecycle is tied
to the pod that defines it - it will be created before the
pod starts, and deleted when the pod is removed. \n Use this
if: a) the volume is only needed while the pod runs, b) features
of normal volumes like restoring from snapshot or capacity
\ tracking are needed, c) the storage driver is specified
through a storage class, and d) the storage driver supports
dynamic volume provisioning through a PersistentVolumeClaim
(see EphemeralVolumeSource for more information on the
connection between this volume type and PersistentVolumeClaim).
\n Use PersistentVolumeClaim or one of the vendor-specific
Expand All @@ -5045,12 +5043,10 @@ spec:
volumes if the CSI driver is meant to be used that way - see
the documentation of the driver for more information. \n A
pod can use both types of ephemeral volumes and persistent
volumes at the same time."
volumes at the same time. \n This is a beta feature and only
available when the GenericEphemeralVolume feature gate is
enabled."
properties:
readOnly:
description: Specifies a read-only configuration for the
volume. Defaults to false (read/write).
type: boolean
volumeClaimTemplate:
description: "Will be used to create a stand-alone PVC to
provision the volume. The pod in which this EphemeralVolumeSource
Expand Down Expand Up @@ -5092,14 +5088,58 @@ spec:
dataSource:
description: 'This field can be used to specify
either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot)
* An existing PVC (PersistentVolumeClaim) * An
existing custom resource that implements data
population (Alpha) In order to use custom resource
types that implement data population, the AnyVolumeDataSource
feature gate must be enabled. If the provisioner
or an external controller can support the specified
data source, it will create a new volume based
on the contents of the specified data source.'
* An existing PVC (PersistentVolumeClaim) If the
provisioner or an external controller can support
the specified data source, it will create a new
volume based on the contents of the specified
data source. If the AnyVolumeDataSource feature
gate is enabled, this field will always have the
same contents as the DataSourceRef field.'
properties:
apiGroup:
description: APIGroup is the group for the resource
being referenced. If APIGroup is not specified,
the specified Kind must be in the core API
group. For any other third-party types, APIGroup
is required.
type: string
kind:
description: Kind is the type of resource being
referenced
type: string
name:
description: Name is the name of resource being
referenced
type: string
required:
- kind
- name
type: object
dataSourceRef:
description: 'Specifies the object from which to
populate the volume with data, if a non-empty
volume is desired. This may be any local object
from a non-empty API group (non core object) or
a PersistentVolumeClaim object. When this field
is specified, volume binding will only succeed
if the type of the specified object matches some
installed volume populator or dynamic provisioner.
This field will replace the functionality of the
DataSource field and as such if both fields are
non-empty, they must have the same value. For
backwards compatibility, both fields (DataSource
and DataSourceRef) will be set to the same value
automatically if one of them is empty and the
other is non-empty. There are two important differences
between DataSource and DataSourceRef: * While
DataSource only allows two specific types of objects,
DataSourceRef allows any non-core object, as
well as PersistentVolumeClaim objects. * While
DataSource ignores disallowed values (dropping
them), DataSourceRef preserves all values, and
generates an error if a disallowed value is specified.
(Alpha) Using this field requires the AnyVolumeDataSource
feature gate to be enabled.'
properties:
apiGroup:
description: APIGroup is the group for the resource
Expand Down Expand Up @@ -5132,7 +5172,7 @@ spec:
pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
x-kubernetes-int-or-string: true
description: 'Limits describes the maximum amount
of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/'
of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/'
type: object
requests:
additionalProperties:
Expand All @@ -5146,7 +5186,7 @@ spec:
is omitted for a container, it defaults to
Limits if that is explicitly specified, otherwise
to an implementation-defined value. More info:
https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/'
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/'
type: object
type: object
selector:
Expand Down
Loading

0 comments on commit 27195db

Please sign in to comment.