I’m looking for information on how key management is implemented in YB (meaning YugabyteDB itself). In general, and in particular when using block-level encryption at rest, how are the keys stored? What happens when the Database is being stopped and then restarted? Do the keys have to be provided by an admin on restart? And if not, how does YB make sure the keys are securely stored (without e.g. some sort of master key)?

How to remove a node from a cluster, so that cluster doesn’t keep reporting it as “down” or red-icon in dashboard ? I suspect yb-admin is needed, but can only find blacklist and blacklist-leader.

How can I easily set host on startup of a yb-container, such that select * from yb_servers() lists a hostname instead of an ip-address in the host column?

Is it possible to change ysqlsh to scroll horizontally instead of wrap long tables and be able to use PgUp and PgDn similar to psql?
I can’t find it in the docs.

How do you escape a password that contains “@“ in connection string?

We found today the issue, that the function yb_is_database_colocated() is missing after an upgrade to 2.18.1.0.

I have 1,000 components each has a separate table row that it update every 10 seconds.
I currently use redis with HSET and HGET.
Is it reasonable to use ysql for this?
Will frequent updates create bloat?
Is automatic full compaction enabled on stable and will take care of that?

Is it possible to know for a specific row on which tablet it resides?

I was looking to get all ip’s of my hosts for all masters and tservers, do we have any specific command through which I can list all of the host ip’s?

I’m just starting testing yugabyte using the yugabyted script. Trying to see if it can replace our current postgresql implementation. The server is running RHEL 8 Linux. I’m getting an error when trying to load a custom function. Any advice would be appreciated.