K8 Configuration
Following are the properties to be updated in MySQL or MSSQL install files.
| Property | Default Value | Description | Additional Information |
|---|---|---|---|
| MSSQL Database Configuration |
The same values in values.yaml will be overwritten if provided in the start scripts. ( Note : Start scripts will be present inside ms-consent-package-docker-<release_number>\ms-consent-docker\k8\on-premise )
|
||
| database_key | sql | Database key | |
| host | consent-db-lbservice | Hostname of database | |
| database_name | ms_consent | Database name | |
| db_username | sa | Username | |
| db_password | Rootroot@12345 | Password | |
| driver_name | com.microsoft.sqlserver.jdbc.SQLServerDriver | Driver Package Name | |
| dialect | org.hibernate.dialect.SQLServer2012Dialect | Database Driver Dialect | |
| db_connection_url | jdbc:sqlserver://consent-db-lbservice:1433;databaseName=ms_consent | URL to connect to the SQL server DB instance | |
| min_pool_size | "10" | database min pool connection | |
| max_pool_size | "150" | database max pool connection | |
| MYSQL Database Configuration | |||
| MYSQL_CRED | "N" | Variable is set to "Y / N", will be enabled or disabled | |
| database_key | sql | Database key | |
| host | consent-db-service | Hostname of database | |
| database_name | ms_consent | Database name | |
| db_username | root | Username | |
| db_password | password | Password | |
| driver_name | com.mysql.cj.jdbc.Driver | Driver Package Name | |
| dialect | org.hibernate.dialect.MySQL5InnoDBDialect | Database Driver Dialect | |
| db_connection_url | jdbc:mysql://consent-db-lbservice:4304/ms_consent?serverTimezone=UTC | URL to connect to the SQL server DB instance | |
| min_pool_size | "10" | database min pool connection | |
| max_pool_size | "150" | database max pool connection | |
| COMMON DB PROPERTIES | |||
| temn_msf_db_pass_encryption_key | temenos | key to decrypt the password | |
| temn_msf_db_pass_encryption_algorithm | PBEWithMD5AndTripleDES | algorithm to decrypt the password | |
|
Security |
|||
| temn_msf_security_authz_enabled | "false" |
Enable / Disable the XACML policy authorization. XACML policy authorization is used to configure security policies and access rights to information for APIs. |
|
| Logger | |||
| logger_root_level | ERROR | ERROR, INFO, and DEBUG are the three values present for logger. | |
| Metrics | |||
| publisherPort | 9091 | ||
| publisherHost | 127.0.0.1 | ||
| metricsDisabled | "true" | ||
| service | |||
|
consentapi: type: LoadBalancer port: 8304 |
A Service in Kubernetes is a REST object, similar to a Pod. Like all of the REST objects, you can POST a Service definition to the API server to create a new instance. Specifies the port, type for the adapterms and API service. When the Service type is set to LoadBalancer, Kubernetes provides functionality equivalent to type equals ClusterIP to pods within the cluster and extends it by programming the (external to Kubernetes) load balancer with entries for the nodes hosting the relevant Kubernetes pod's | ||
| logging | |||
|
socketHost: 127.0.0.1 socketPort: 9092 exportType: #"socket" |
Logging will be collecting, storing, and analyzing distributed logs. Here Logstash is used for creating an ingestion pipeline for collecting logs from multiple devices and store in Elasticsearch storage for visualizing and analyzing through Grafana.To enable logging sockethost, SockerPort, and exportType, the protocol should be uncommented and the required port and host address should be given. | ||
| Resources | |||
|
API: memoryrequest: 1G memorylimit: 2G java:heaplimit: ' -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -XX:MaxRAMPercentage=75.0 ' |
Resource management for pods / Containers -- Kubernetes uses to control resources such as CPU and memory can declare limits for CPU and memory for all pod containers. cpu limit --The CPU limit defines a hard ceiling on how much CPU time the container can use. it should not be less than 1M. can a specific CPU limit be 1M or 0.001 memory limit – If you specify a memory limit for every container in a Pod, Kubernetes can infer the Pod-level memory limit by adding up the limits for its containersheapLimitTo change the value of experimental flags, you must unlock them first. You can do this by setting -XX:+UnlockExperimentalVMOptions explicitly on the command line before any experimental flagsThe flag -XX:+UseCGroupMemoryLimitForHeap lets the JVM detect what the max heap size in a container should be.MaxRAMPercentage parameter allows setting the maximum heap size for a JVM running with a large amount of memory (greater than 200 MB). |
||
In this topic