text stringlengths 0 59.1k |
|---|
- containerPort: 6666 |
hostPort: 6666 |
securityContext: |
privileged: true |
env: |
- name: ACCESS_KEY #REQUIRED - replace with your Sysdig Cloud access key |
value: 8312341g-5678-abcd-4a2b2c-33bcsd655 |
# - name: K8S_DELEGATED_NODE #OPTIONAL - only necessary when connecting remotely to API server |
# value: <DELEGATED NODE IP> |
# - name: K8S_API_URI #OPTIONAL - only necessary when connecting remotely to API server |
# value: "http[s]://[username:passwd@]host[:port]" |
# - name: TAGS #OPTIONAL |
# value: linux:ubuntu,dept:dev,local:nyc |
# - name: COLLECTOR #OPTIONAL |
# value: 192.168.183.200 |
# - name: SECURE #OPTIONAL |
# value: false |
# - name: CHECK_CERTIFICATE #OPTIONAL |
# value: false |
# - name: ADDITIONAL_CONF #OPTIONAL |
# value: "app_checks:\n - name: nginx\n check_module: nginx\n pattern:\n comm: nginx\n conf:\n nginx_status_url: "http://localhost:{port}/nginx_status\"" |
volumeMounts: |
- mountPath: /host/var/run/docker.sock |
name: docker-sock |
readOnly: false |
- mountPath: /host/dev |
name: dev-vol |
readOnly: false |
- mountPath: /host/proc |
name: proc-vol |
readOnly: true |
- mountPath: /host/boot |
name: boot-vol |
readOnly: true |
- mountPath: /host/lib/modules |
name: modules-vol |
readOnly: true |
- mountPath: /host/usr |
name: usr-vol |
readOnly: true |
<|endoftext|> |
# source: k8s_examples/_archived/sysdig-cloud/README.md type: docs |
[Sysdig Cloud](http://www.sysdig.com/) is a monitoring, alerting, and troubleshooting platform designed to natively support containerized and service-oriented applications. |
Sysdig Cloud comes with built-in, first class support for Kubernetes. In order to instrument your Kubernetes environment with Sysdig Cloud, you simply need to install the Sysdig Cloud agent container on each underlying host in your Kubernetes cluster. Sysdig Cloud will automatically begin monitoring all of your hosts, ... |
# Example Installation Files |
Provided here are two example sysdig.yaml files that can be used to automatically deploy the Sysdig Cloud agent container across a Kubernetes cluster. |
The recommended method is using daemon sets - minimum kubernetes version 1.1.1. |
If daemon sets are not available, then the replication controller method can be used (based on [this hack](https://stackoverflow.com/questions/33377054/how-to-require-one-pod-per-minion-kublet-when-configuring-a-replication-controll/33381862#33381862 )). |
# Latest Files |
See here for the latest maintained and updated versions of these example files: |
https://github.com/draios/sysdig-cloud-scripts/tree/master/agent_deploy/kubernetes |
# Install instructions |
Please see the Sysdig Cloud support site for the latest documentation: |
http://support.sysdigcloud.com/hc/en-us/sections/200959909 |
<|endoftext|> |
# source: k8s_examples/_archived/cluster-dns/dns-backend-rc.yaml type: yaml |
apiVersion: v1 |
kind: ReplicationController |
metadata: |
name: dns-backend |
labels: |
name: dns-backend |
spec: |
replicas: 1 |
selector: |
name: dns-backend |
template: |
metadata: |
labels: |
name: dns-backend |
spec: |
containers: |
- name: dns-backend |
image: registry.k8s.io/example-dns-backend:v2 |
ports: |
- name: backend-port |
containerPort: 8000 |
<|endoftext|> |
# source: k8s_examples/_archived/cluster-dns/dns-backend-service.yaml type: yaml |
kind: Service |
apiVersion: v1 |
metadata: |
name: dns-backend |
spec: |
ports: |
- port: 8000 |
selector: |
name: dns-backend |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.