Configuring InfoScale

InfoScale logs in Kubernetes and OpenShift environments persist beyond container lifecycles via hostPath directories (/var/VRTS/log) and can be aggregated using EFK stacks or Fluentd daemonsets. Fluentd provides a robust solution for collecting container logs across all nodes, requiring privileged security context to access host volumes. For Disaster Recovery (DR) configurations, controller logs should be integrated into the Fluentd log collection process to ensure visibility across all peer clusters.

To enhance performance, InfoScale Oracle Data Manager (VRTSodm) allows Oracle applications to bypass standard file system caching by linking the libodm.so library and routing I/O calls through the ODM kernel module. Enabling this requires specific configuration adjustments within the database deployment YAML, including the use of initContainers for volume permissions, disabling Direct NFS (DNFS), and mounting the hostpath /dev/odm while running the container in privileged mode.

Comprehensive auditing is available by configuring the Kubernetes API server manifest, which allows for detailed tracking of system events, process activity, and user login attempts. Administrators can implement audit policies to monitor pod executions, resource modifications, and configuration changes. Furthermore, enabling the EO_COMPLIANCE environment variable within the InfoScale operator deployment provides extended logging for core components such as VxVM, VxFS, and VCS, ensuring full operational visibility and compliance across the cluster.