You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to clarify that running the following sequency during database bootstrapping does solve this problem. But it would be nice to be able to enforce this from the consumer side (if this sql is not ran for any reason, the public schema is used again).
CREATESCHEMAk3s;
ALTERDATABASE db SET search_path to k3s;
That's an issue, not a PR. Nothing has been changed to allow this. If you'd like to see this fixed, it will require changes to kine. A PR would be welcome.
This may not be relevant for a lot of people, but by default k3s/kine creates it's tables under the
public
schema. As you may or may not know, any user in the database can thus access this data by default.As k3s is mainly for small clusters, I doubt users care about this level of isolation, but in my case I definitely do 😆.
Is it possible to specify another schema then
public
with the postgresql endpoint?Thanks a lot!!!
The text was updated successfully, but these errors were encountered: