The returned certificate is the public certificate (which includes the public key but not the private key), which itself can be in a couple of formats.
this is a container format that may include just the public certificate (such as with Apache installs, and CA certificate files /etc/ssl/certs), or may include an entire certificate chain including public key, private key, and root certificates
Privacy Enhanced Mail (PEM), a failed method for secure email but the container format it used lives on
This is a PEM formatted file containing just the private-key of a specific certificate and is merely a conventional name and not a standardized one.
The rights on these files are very important
/etc/ssl/private
OpenSSL can convert these to .pem
.cert .cer .crt A .pem (or rarely .der) formatted file with a different extension
there are four different ways to present certificates and their components
used preferentially by open-source software
It can have a variety of extensions (.pem, .key, .cer, .cert, more)
The parent format of PEM
a binary version of the base64-encoded PEM file.
PEM on it's own isn't a certificate, it's just a way of encoding data
X.509 certificates are one type of data that is commonly encoded using PEM.
before(:all) hooks are invoked before the transaction is opened. You can use
this to speed things up by creating data once before any example in a group is
run
"Welcome to the Alchemy system! Alchemy is a software package providing a series of algorithms for statistical relational learning and probabilistic logic inference, based on the Markov logic representation. Alchemy allows you to easily develop a wide range of AI applications, including:"
Communication between pods is more complicated, however, and requires a separate networking component that can transparently route traffic from a pod on one node to a pod on another.
pod network plugins. For this cluster, you will use Flannel, a stable and performant option.
Passing the argument --pod-network-cidr=10.244.0.0/16 specifies the private subnet that the pod IPs will be assigned from.
kubectl apply -f descriptor.[yml|json] is the syntax for telling kubectl to create the objects described in the descriptor.[yml|json] file.
deploy Nginx using Deployments and Services
A deployment is a type of Kubernetes object that ensures there's always a specified number of pods running based on a defined template, even if the pod crashes during the cluster's lifetime.
NodePort, a scheme that will make the pod accessible through an arbitrary port opened on each node of the cluster
Services are another type of Kubernetes object that expose cluster internal services to clients, both internal and external.
load balancing requests to multiple pods
Pods are ubiquitous in Kubernetes, so understanding them will facilitate your work
how controllers such as deployments work since they are used frequently in stateless applications for scaling and the automated healing of unhealthy applications.
Understanding the types of services and the options they have is essential for running both stateless and stateful applications.
HTTP is meant to run over a bidirectional tunnel for arbitrary binary data; when that tunnel is an SSL/TLS connection, then the whole is called "HTTPS".
"SSL" means "Secure Sockets Layer".
"TLS" means "Transport Layer Security".
The name was changed to avoid any legal issues with Netscape so that the protocol could be "open and free" (and published as a RFC).
"HTTPS" is supposed to mean "HyperText Transfer Protocol Secure",
Other protocol acronyms have been built the same way, e.g. SMTPS, IMAPS, FTPS... all of them being a bare protocol that "got secured" by running it within some SSL/TLS.
To make the confusing perfect: SSL (secure socket layer) often refers to the old protocol variant which starts with the handshake right away and therefore requires another port for the encrypted protocol such as 443 instead of 80.
TLS (transport layer security) often refers to the new variant which allows to start with an unencrypted traditional protocol and then issuing a command (usually STARTTLS) to initialize the handshake.
Whether you use SSL or TLS for this depends on the configuration of your browser and of the server (there usually is an option to allow SSLv2, SSLv3 or TLS 1.x).