OntapFileSystem is the Schema for the OntapFileSystems API. Manages an Amazon FSx for NetApp ONTAP file system.
Type
CRD
Group
fsx.aws.upbound.io
Version
v1beta1
apiVersion: fsx.aws.upbound.io/v1beta1
kind: OntapFileSystem
OntapFileSystemSpec defines the desired state of OntapFileSystem
No description provided.
Reference to a Key in kms to populate kmsKeyId.
Policies for referencing.
Selector for a Key in kms to populate kmsKeyId.
Policies for selection.
Reference to a Subnet in ec2 to populate preferredSubnetId.
Policies for referencing.
Selector for a Subnet in ec2 to populate preferredSubnetId.
Policies for selection.
Specifies the VPC route tables in which your file system's endpoints will be created. You should specify all VPC route tables associated with the subnets in which your clients are located. By default, Amazon FSx selects your VPC's default route table.
References to SecurityGroup in ec2 to populate securityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroupIds.
Policies for selection.
A list of IDs for the security groups that apply to the specified network interfaces created for file system access. These security groups will apply to all network interfaces.
References to Subnet in ec2 to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnetIds.
Policies for selection.
A list of IDs for the subnets that the file system will be accessible from. Upto 2 subnets can be provided.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
OntapFileSystemStatus defines the observed state of OntapFileSystem.
No description provided.
The endpoints that are used to access data or to manage the file system using the NetApp ONTAP CLI, REST API, or NetApp SnapMirror. See Endpoints below.
An endpoint for managing your file system by setting up NetApp SnapMirror with other ONTAP systems. See Endpoint.
IP addresses of the file system endpoint.
An endpoint for managing your file system using the NetApp ONTAP CLI and NetApp ONTAP API. See Endpoint.
IP addresses of the file system endpoint.
Set of Elastic Network Interface identifiers from which the file system is accessible The first network interface returned is the primary network interface.
Conditions of the resource.
test
apiVersion: fsx.aws.upbound.io/v1beta1
kind: OntapFileSystem
metadata:
annotations:
meta.upbound.io/example-id: fsx/v1beta1/ontapstoragevirtualmachine
labels:
testing.upbound.io/example-name: test
name: test
spec:
forProvider:
automaticBackupRetentionDays: 0
deploymentType: SINGLE_AZ_1
preferredSubnetIdSelector:
matchLabels:
testing.upbound.io/example-name: test1
region: us-east-1
storageCapacity: 1024
subnetIdRefs:
- name: test1
throughputCapacity: 128
test
apiVersion: fsx.aws.upbound.io/v1beta1
kind: OntapFileSystem
metadata:
annotations:
meta.upbound.io/example-id: fsx/v1beta1/ontapfilesystem
uptest.upbound.io/timeout: "5400"
labels:
testing.upbound.io/example-name: test
name: test
spec:
forProvider:
automaticBackupRetentionDays: 0
deploymentType: SINGLE_AZ_1
preferredSubnetIdSelector:
matchLabels:
testing.upbound.io/example-name: test1
region: us-east-1
storageCapacity: 1024
subnetIdRefs:
- name: test1
throughputCapacity: 128
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.