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
Users now have an SSH container with a generated private key. Users no longer need to authenticate with premade cert and key. Service account bound to ssh pod allowing users to run kubectl via the SSH session.
Resolves#1#3 and partial resolution of #4 in the sense of PID running and mounting
* RCON Port Correction
* Backup Integration
Backup Integration
Uses Stash.
Every midnight
* New Values
New configurable values based on itzg/minecraft-server and s3 backup values.
* Altered backup manifest
* Change user auth type to service-account
For running/easy mounting of kubectl in pod
* Updated server deployment
Users now have an SSH container with a generated private key. Users no longer need to authenticate with premade cert and key. Service account bound to ssh pod allowing users to run kubectl via the SSH session.
Resolves#1#3 and partial resolution of #4 in the sense of PID running and mounting
* Moved DNS updates and mail notification to job
Uses mounted secrets. Note: User service acocunt is not allowed to read secrets.
* Chart Update
Chart update
Version 2.0 release
Implement proper pod security policies to move towards goal of giving users Namespace limits vs predefined stateful set limits.
https://kubernetes.io/docs/concepts/policy/pod-security-policy/
The text was updated successfully, but these errors were encountered: