When database.conf is defined, the below warning is triggered during startup. The permissions are correct (root:root) and likely don't ever need an update in an k8s environment. I guess the check comes from an internal WB process but is likely only relevant for non-k8s envs?
Would be good to account for it as one cannot do so because the referenced mount is initiated by the chart. AFAICS this affects all deployments which don't use the built-in SQLITE DB.
2024-01-09T15:53:17.928385Z [rserver] WARNING Failed attempt to update ownership of database configuration file /mnt/secret-configmap/rstudio/database.conf to root user: Read-only file system - please ensur │
│ e that the file owner is root if it contains sensitive information; LOGGED FROM: rstudio::core::Error rstudio::server_core::database::{anonymous}::readOptions(const string&, const rstudio_boost::optional<rs │
│ tudio::core::system::User>&, rstudio::core::database::ConnectionOptions*, std::string) src/cpp/server_core/ServerDatabase.cpp:343
When
database.conf
is defined, the below warning is triggered during startup. The permissions are correct (root:root
) and likely don't ever need an update in an k8s environment. I guess the check comes from an internal WB process but is likely only relevant for non-k8s envs?Would be good to account for it as one cannot do so because the referenced mount is initiated by the chart. AFAICS this affects all deployments which don't use the built-in SQLITE DB.