Skip to content

Allow to define SSL keys for configuration and chown then for proper usage#205

Open
iranzo wants to merge 11 commits into
paunin:masterfrom
iranzo:sslkeyschown
Open

Allow to define SSL keys for configuration and chown then for proper usage#205
iranzo wants to merge 11 commits into
paunin:masterfrom
iranzo:sslkeyschown

Conversation

@iranzo

@iranzo iranzo commented Dec 14, 2018

Copy link
Copy Markdown

Allow to define ssl settings via environment variable and check them on /pg-ssl secret in kubernetes so that keys are copied and chowned to end folder:

CONFIGS: ssl:on,ssl_cert_file:'/etc/postgresql/server.crt',ssl_key_file:'/etc/postgresql/server.key'
And provide a secret like:

apiVersion: v1
data:
server.crt: >-
YOURSECRET
server.key: >-
YOURSECRET
kind: Secret
metadata:
name: postgres
namespace: YOURNAMESPACE
selfLink: /api/v1/namespaces/quay-enterprise/secrets/postgres
type: Opaque
That must be mounted on /pg-ssl

@paunin

paunin commented Apr 27, 2019

Copy link
Copy Markdown
Owner

Need some tests if you go for SSL.
Also better to have some examples of usage.

@iranzo

iranzo commented Apr 30, 2019

Copy link
Copy Markdown
Author

Blog post is pending, I'll update once it is finalized and released

@cooktheryan

Copy link
Copy Markdown

@paunin is there any way we can help with the testing to get this merged

@paunin

paunin commented May 28, 2019

Copy link
Copy Markdown
Owner

@cooktheryan Yes. Add some

  • documentation about usage of the feature
  • tests that feature works as designed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants