-
Notifications
You must be signed in to change notification settings - Fork 66
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.
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
[WIP] Configure TLS for Kubernetes services #351
base: master
Are you sure you want to change the base?
Conversation
7a04f47
to
a709038
Compare
default: | ||
"classpath://io.brooklyn.clocker.kubernetes:kubernetes/basic_auth.csv" | ||
"classpath://io.brooklyn.clocker.kubernetes:kubernetes/policy.jsonl" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this file called .jsonl
? Is that a typo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's an awful format called JSON List which is a series of concatenated JSON objects!
sudo mkdir /etc/kubernetes/certs | ||
sudo chown ${USER} /etc/kubernetes/certs | ||
source ${INSTALL_DIR}/certificate-functions.sh | ||
getcert ${CA_REQUEST_ROOT_URL}/cacert/ca.pem /etc/kubernetes/certs/ca.pem |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit uncomfortable about this. It means the blueprint can't be used with an enterprise's existing CA server, if it does not support this REST api. I wonder if that could be customized by supplying your own certificate-functions.sh
(but that script is not customizable).
This is probably a much bigger conversation though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, but that is a change that should be applied to all entities in Clocker that use TLS and the CA server
ee4b8d5
to
c1a484c
Compare
No description provided.