Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Immediate termination of SSH access #4

Closed
sfxworks opened this issue May 17, 2019 · 0 comments
Closed

Immediate termination of SSH access #4

sfxworks opened this issue May 17, 2019 · 0 comments

Comments

@sfxworks
Copy link
Contributor

Reappending

        tty: true
        stdin: true

Does not yield an active ssh container.
This is either related to the new RBAC roles allowed, preventing exec, or related to the container.

Example provided by user:

> kubectl port-forward deployment/lunging-mastiff-server 2202:22
Forwarding from 127.0.0.1:2202 -> 22
Forwarding from [::1]:2202 -> 22
Handling connection for 2202

(separate terminal)
> ssh -4 -p 2202 root@localhost
root@localhost's password: 
Shared connection to localhost closed.
sfxworks added a commit that referenced this issue Jun 10, 2019
@sfxworks
Updated server deployment
e2c03a4 
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
sfxworks added a commit that referenced this issue Jun 10, 2019
@sfxworks
Helm Chart 2.0 Release (#5)
991d5a3 
* 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
sfxworks added a commit that referenced this issue Sep 3, 2019
@sfxworks
Helm Chart 2.0 Release (#5)
219506f 
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sfxworks