Advanced Clusters > Advanced configurations > Self-service cluster properties

Self-service cluster properties

Create an advanced configuration to configure properties for an advanced cluster. The properties describe where you want to start the cluster on your cloud platform and the infrastructure that you want to use.

The basic properties describe the advanced configuration and define the cloud platform that hosts the self-service cluster. To configure the cluster, configure the platform and runtime properties.

To learn about the minimum resource specifications that you need to set up a self-service cluster to run a mapping, see Resource requirements for cluster nodes.

Basic configuration

The following table describes the basic properties:

Property	Description
Name	Name of the advanced configuration.
Description	Description of the advanced configuration.
Runtime Environment	Runtime environment to associate with the advanced configuration. The runtime environment can contain only one Secure Agent. A runtime environment cannot be associated with more than one configuration. If you don't select a runtime environment, the validation process can't validate the communication link to the Secure Agent and that the Secure Agent has the minimum runtime requirements to start a cluster.
Cloud Platform	Cloud platform that hosts the cluster. Select Self-Service Cluster.

Platform configuration

The following table describes the platform properties:

Property	Description
Kubeconfig File Path	Path of the kubeconfig file. A kubeconfig file organizes information about clusters, users, and authentication mechanisms. Example: <directory name>/<file_name>.yaml You can save the YAML file in any directory on the Secure Agent machine.
Kube Context Name	Name of the cluster context. A context defines a named cluster and user tuple which is used to send requests to the specified cluster using the provided authentication information.
Cluster Version	Version of the Kubernetes cluster server. The advanced configuration validates the major and minor versions of the Kubernetes cluster server, but does not validate the patch release version numbers.
Namespace	Namespace where Informatica deploys resources.
Number of Worker Nodes	Number of worker nodes in the cluster. Specify the minimum and maximum number of worker nodes.
Cluster Idle Timeout	Amount of time before Informatica-created cluster resource objects are deleted due to inactivity.
Mapping Task Timeout	Amount of time to wait for a mapping task to complete before it is terminated. By default, a mapping task does not have a timeout. If you specify a timeout, a value of at least 10 minutes is recommended. The timeout begins when the mapping task is submitted to the Secure Agent.
Staging Location	Complete path of the cloud location for staging data. Specify the path in one of the following formats: - AWS. s3://<bucket name>/<folder path> Note: Specify an S3 bucket in the same region as the cluster to decrease latency. - Microsoft Azure. abfs(s)://<file system>@<storage account>.dfs.core.windows.net/<folder path>&:<resource group>/<region> The region is optional. The default region is westus2. The Secure Agent needs permissions to access the staging location to store staging files at run time. You must provide appropriate IAM access permissions to both the Secure Agent machine and the worker nodes running in your cluster to access the staging location.
Log Location	Complete path of the cloud location for storing logs. Specify the path in one of the following formats: - AWS. s3://<bucket name>/<folder path> Note: Specify an S3 bucket in the same region as the cluster to decrease latency. - Microsoft Azure. abfs(s)://<file system>@<storage account>.dfs.core.windows.net/<folder path>&:<resource group>/<region> The region is optional. The default region is westus2. The Secure Agent needs permissions to access the staging location to store staging files at run time. You must provide appropriate IAM access permissions to both the Secure Agent machine and the worker nodes running in your cluster to access the staging location.
Labels	Key-value pairs that Informatica attaches to the Kubernetes objects that it creates in the self-service cluster. You can use labels to organize and select subsets of objects. Each object can have a set of key-value labels defined. Each key must be unique for a given object. You cannot use the @ symbol in a label. For more information about the supported syntax and character set, see the Kubernetes documentation.
Node Selector Labels	Use node selector labels to identify the nodes in the cluster on which Informatica can create Kubernetes objects.

Advanced configuration

The following table describes the advanced properties:

Property	Description
Annotations	Key-value pairs that are used to attach arbitrary non-identifying metadata to objects. You can only define annotations for Pods in a cluster. For more information about annotations, see the Kubernetes documentation.
Tolerations	Key-value pairs that are used to ensure that Pods are scheduled on appropriate nodes. When you configure a toleration, set the following properties: - Key - Operator - Value - Effect - Toleration Seconds For more information about tolerations, see the Kubernetes documentation.

Runtime configuration

The following table describes the runtime properties:

Property	Description
Encrypt Data	Indicates whether temporary data on the cluster is encrypted. Note: Encrypting temporary data might slow down job performance.
Runtime Properties	Custom properties to customize the cluster and the jobs that run on the cluster.

Runtime Properties

The following table describes the runtime properties that you can use to customize a self-service cluster and the jobs that run on the cluster:

Property	Description
infa.k8s.deploy.clusterkeygen.enable	Manages clusterkeygen deployment. Set this property to false to disable the deployment.
infa.k8s.custom.quota.name	Specifies the quota name if defined in the cluster.
ccs.app.control.enable	Manages application submission control. Set this property to false to disable the submission control. You can use the application submission control only if all of the following conditions are true: - All the cluster nodes are homogeneous. - The namespace or nodes are reserved for Informatica. Informatica can read the node details. - The namespace quota, if present, is honored and the quota name can be configured using custom flag. When you define a quota on the cluster, you can use only the request in quota definition. Don't use limit in the quota definition because if you define the limits for the resources that you deploy, the resources won't get scheduled.
infacco.job.spark.kubernetes.scheduler.name	Specifies the custom scheduler name for driver and executor pods.

Validating the configuration

You can validate the information needed to create or update an advanced configuration before you save the configuration properties.

The validation process performs the following validations:

•You have provided the necessary information on the configuration page.
•The information you provided is valid or in the correct format. For example, the runtime environment shouldn't be associated with another advanced configuration.

Note: The validation process doesn't validate whether cloud resources have been configured correctly, such as whether cloud roles have all the necessary permissions.