I. Introduction 1. Kubernetes Overview - Kubernetes = popular container orchestrator * it lets you schedule containers on a cluster of machines * you can run multiple containers on one machine * you can run long running services (like web applications) * Kubernetes will manage the state of those containers: ** Can start the container on specific nodeskubectl create -f pod-demo.yml ** Will restart a container when it gets killed ** Can move containers from one dnode to another node - you can run Kubernetes anywhere: *on-premise (own datacenter) *public (Google cloud, AWS) *hybrid: public & private -highly modular -open source -backed by google -Container Orchestration = Make many servers act like one -Released by Google in 2015, maintained by large community -Runs on top of Docker (usually) as a set of APIs in containers -Provides API/CLI to managed containers across server...
1. Overview 1.1 Splunk Enterprise Overview Splunk Enterprise Features a) Index -Source data from websites, applications, servers, databses and more -Index your IT data into Splunk b) Search -Primary way you will navigate youre data in splunk -Search can also be used as report to power dashobard panels c) Alerts -Get notified when search results meet specific conditions -Alert actions can spend an email, post to an RSS feed, or execute a script d) Dashoboards -Combine panels into a wholistic view of your data -Panels can contain search boxes, fields, charts, and more e) Pivot -Map attributes to a table, chart, or data visualization -Can be saved as raports and added to dashboards f) Reports -Save searches as pivot reports and then add reports to dashboards as panels -Run them ad-hoc or on a schedulde Splunk Enterprise Components a) Forwarder -Collects and forwards data to an indexer -Low resource usage allowing them to reside on many machin...
0. Overivew - Packet manager 1. Helm Provenance and Integrity - https://github.com/technosophos/k8s-helm/blob/master/docs/provenance.md - Helm has provenance tools which help chart users verify the integrity and origin of a package. Using industry-standard tools based on PKI, GnuPG, and well-respected package managers, Helm can generate and verify signature files. a) Overview - I ntegrity is established by comparing a chart to a provenance record. Provenance records are stored in provenance files , which are stored alongside a packaged chart. For example, if a chart is named myapp-1.2.3.tgz , its provenance file will be myapp-1.2.3.tgz.prov . - Provenance files are generated at packaging time ( helm package --sign ... ), and can be checked by multiple commands, notable helm install --verify . b) The workflow This section describes a potential workflow for using provenance data effectively. Prerequisites: A valid PGP keyp...
Komentarze
Prześlij komentarz