mirror of https://github.com/k3s-io/k3s
f06dc326d3
Automatic merge from submit-queue fixes invalid null selector issue in sysdig example yaml <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: Using the file DaemonSet yaml found in the example repo you get the following error upon import: ``` $ kubectl create -f sysdig.yml The DaemonSet "sysdig-agent" is invalid. spec.template.metadata.labels: Invalid value: null: `selector` does not match template `labels` ``` This PR fixes this issue. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note ``` * Corrected name label metadata for Sysdig example. |
||
|---|---|---|
| .. | ||
| apiserver | ||
| cluster-dns | ||
| cockroachdb | ||
| elasticsearch | ||
| experimental/persistent-volume-provisioning | ||
| explorer | ||
| guestbook | ||
| guestbook-go | ||
| https-nginx | ||
| javaee | ||
| javaweb-tomcat-sidecar | ||
| job | ||
| k8petstore | ||
| kubectl-container | ||
| meteor | ||
| mysql-cinder-pd | ||
| mysql-wordpress-pd | ||
| newrelic | ||
| nodesjs-mongodb | ||
| openshift-origin | ||
| phabricator | ||
| runtime-constraints | ||
| selenium | ||
| sharing-clusters | ||
| spark | ||
| storage | ||
| storm | ||
| sysdig-cloud | ||
| volumes | ||
| OWNERS | ||
| README.md | ||
| doc.go | ||
| examples_test.go | ||
| guidelines.md | ||
| pod | ||
| scheduler-policy-config-with-extender.json | ||
| scheduler-policy-config.json | ||
| simple-nginx.md | ||
README.md
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.4/examples/README.md).Documentation for other releases can be found at releases.k8s.io.
Kubernetes Examples: releases.k8s.io/HEAD
This directory contains a number of examples of how to run real applications with Kubernetes.
Demonstrations of how to use specific Kubernetes features can be found in our documents.
Maintained Examples
Maintained Examples are expected to be updated with every Kubernetes release, to use the latest and greatest features, current guidelines and best practices, and to refresh command syntax, output, changed prerequisites, as needed.
| Name | Description | Notable Features Used | Complexity Level | |
|---|---|---|---|---|
| Guestbook | PHP app with Redis | Replication Controller, Service | Beginner | |
| WordPress | WordPress with MySQL | Deployment, Persistent Volume with Claim | Beginner | |
| Cassandra | Cloud Native Cassandra | Daemon Set | Intermediate |
Note: Please add examples to the list above that are maintained.
See Example Guidelines for a description of what goes in this directory, and what examples should contain.