A short survey of log collection options and why you picked the wrong one. 😜
I'm Steve Coffman and I work at Ithaka. We do JStor (academic journals) and other stuff. How big is it?
Number | what it means |
---|---|
101,332,633 | unique visitors in 2017 |
apiVersion: apps/v1 | |
kind: StatefulSet | |
metadata: | |
name: elasticsearch | |
labels: | |
service: elasticsearch | |
spec: | |
serviceName: es | |
# NOTE: This is number of nodes that we want to run | |
# you may update this |
FROM centos:7 | |
# Install dependencies | |
RUN yum install -y yum-utils gcc git | |
# Enable OpenResty repo (see RHEL section at https://openresty.org/en/linux-packages.html) | |
RUN yum-config-manager --add-repo https://openresty.org/package/centos/openresty.repo | |
# Enable EPEL packages (needed for LuaRocks) | |
RUN yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm |
apiVersion: extensions/v1beta1 | |
kind: DaemonSet | |
metadata: | |
name: filebeat | |
namespace: kube-system | |
labels: | |
k8s-app: filebeat | |
spec: | |
template: | |
metadata: |
Thanks a lot to mredbishop and others for their insturctions posted here. This is just a recap of what they figured out.
This process was tested on WSL Ubuntu 18.04.
For example your latest image with semantic versioning looks like this:
${DOCKER_HUB_ORG}/${DOCKER_HUB_REPO}:v1.20.0
Example provided above will do the folowing:
The view ClusterRole doesn’t actually have permissions for the Cluster level objects like Nodes and Persistent Volume Claims. So we’ll have to create a new RBAC config.
First, we’ll create a new dashboard-viewonly ClusterRole:
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: dashboard-viewonly