Skip to content

Conversation

@sebgoa
Copy link
Contributor

@sebgoa sebgoa commented May 1, 2017

PR to migrate the examples to dedicated kubernetes/examples repo.

This preserves history.

Cleanup of source in kubernetes/kubernetes will happen after this gets merged.

humblec and others added 30 commits October 20, 2016 00:31
Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
Automatic merge from submit-queue

Add vSphere Volume Examples

This PR adds vSphere Volume Examples
Signed-off-by: Huamin Chen <hchen@redhat.com>
update client-gen to use the term "internalversion" rather than "unversioned";
leave internal one unqualified;
cleanup client-gen
Kubernetes now checks that secrets used for provisioning of volumes
have correct type (PR #35675), all examples should reflect it.
* Use an init container to eliminate potential edge case where losing
  the first pet's could cause it to start a second logical cluster
* Exec the cockroach binary so that it runs as PID 1 in the container
* Make some small improvements to the README
Automatic merge from submit-queue

support Azure disk dynamic provisioning

azure disk dynamic provisioning

A screen shot 

``` console
$ kubectl create -f examples/experimental/persistent-volume-provisioning/azure-dd.yaml
storageclass "slow" created
$ kubectl create -f examples/experimental/persistent-volume-provisioning/claim1.json
persistentvolumeclaim "claim1" created
$ kubectl describe pvc
Name:       claim1
Namespace:  default
Status:     Bound
Volume:     pvc-de7150d1-6a37-11e6-aec9-000d3a12e034
Labels:     <none>
Capacity:   3Gi
Access Modes:   RWO
$ kubectl create -f pod.yaml
replicationcontroller "nfs-server" created
$ kubectl describe pod
Name:       nfs-server-b9w6x
Namespace:  default
Node:       rootfs-dev/172.24.0.4
Start Time: Wed, 24 Aug 2016 19:46:21 +0000
Labels:     role=nfs-server
Status:     Running
IP:     172.17.0.2
Controllers:    ReplicationController/nfs-server
Containers:
  nfs-server:
    Container ID:   docker://be6f8c0e26dc896d4c53ef0d21c9414982f0b39a10facd6b93a255f9e1c3806c
    Image:      nginx
    Image ID:       docker://bfdd4ced794ed276a28cf56b233ea58dec544e9ca329d796cf30b8bcf6d39b3f
    Port:       
    State:      Running
      Started:      Wed, 24 Aug 2016 19:49:19 +0000
    Ready:      True
    Restart Count:  0
    Volume Mounts:
      /exports from mypvc (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-9o0fj (ro)
    Environment Variables:  <none>
Conditions:
  Type      Status
  Initialized   True 
  Ready     True 
  PodScheduled  True 
Volumes:
  mypvc:
    Type:   PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  claim1
    ReadOnly:   false
  default-token-9o0fj:
    Type:   Secret (a volume populated by a Secret)
    SecretName: default-token-9o0fj
QoS Class:  BestEffort
Tolerations:    <none>
Events:
  FirstSeen LastSeen    Count   From            SubobjectPath           Type        Reason      Message
  --------- --------    -----   ----            -------------           --------    ------      -------
  11m       11m     1   {default-scheduler }                    Normal      Scheduled   Successfully assigned nfs-server-b9w6x to rootfs-dev
  9m        9m      1   {kubelet rootfs-dev}                    Warning     FailedMount Unable to mount volumes for pod "nfs-server-b9w6x_default(6eb7fd98-6a33-11e6-aec9-000d3a12e034)": timeout expired waiting for volumes to attach/mount for pod "nfs-server-b9w6x"/"default". list of unattached/unmounted volumes=[mypvc]
  9m        9m      1   {kubelet rootfs-dev}                    Warning     FailedSync  Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "nfs-server-b9w6x"/"default". list of unattached/unmounted volumes=[mypvc]
  8m        8m      1   {kubelet rootfs-dev}    spec.containers{nfs-server} Normal      Pulling     pulling image "nginx"
  8m        8m      1   {kubelet rootfs-dev}    spec.containers{nfs-server} Normal      Pulled      Successfully pulled image "nginx"
  8m        8m      1   {kubelet rootfs-dev}    spec.containers{nfs-server} Normal      Created     Created container with docker id be6f8c0e26dc
  8m        8m      1   {kubelet rootfs-dev}    spec.containers{nfs-server} Normal      Started     Started container with docker id be6f8c0e26dc

```

@colemickens @brendandburns
… apps/v1alpha1 files

Manually remove generated apps/v1alpha1 types, protobuf, and api-reference doc files
Manually remove apps/v1alpha1 folder from 1.5 generated client
Automatic merge from submit-queue

Move Statefulset (previously PetSet) to v1beta1

**What this PR does / why we need it**: #28718

**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**: depends on #35663 (PetSet rename)
cc @erictune @foxish @kubernetes/sig-apps 

**Release note**:

``` release-note
v1beta1/StatefulSet replaces v1alpha1/PetSet.
```
Signed-off-by: Huamin Chen <hchen@redhat.com>
Automatic merge from submit-queue

Update Secret.type examples used for provisioning.

Kubernetes now checks that secrets used for provisioning of volumes
have correct type (PR #35675), all examples should reflect it.
Automatic merge from submit-queue

Rename PetSet to StatefulSet in docs and examples.

**What this PR does / why we need it**: Addresses some of the pre-code-freeze changes for implementing the PetSet --> StatefulSet rename. (#35534)

**Special notes for your reviewer**: This PR only changes docs and examples, as #35731 hasn't been merged yet and I don't want to create merge conflicts. I'll open another PR for any remaining code changes needed after that PR is merged. /cc @erictune @janetkuo @chrislovecnm
metachris and others added 20 commits April 2, 2017 11:27
Updated the GlusterFS `README.md` to fix several typos, outdated documentation and examples that did not work anymore.

Updated examples/volumes/glusterfs/README.md with better examples

Updated the examples/volumes/glusterfs README with a better explanation of the endpoints attribute
Automatic merge from submit-queue

relocate FC multipath readme to examples from pkg/volume

Signed-off-by: rootfs <hchen@redhat.com>



**What this PR does / why we need it**:
`pkg/volume/README.md` is not a good place for Fiber Channel specific doc. Move the block into FC README.
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:

```release-note
NONE
```
Automatic merge from submit-queue

fix satisfy typo
Signed-off-by: Huamin Chen <hchen@redhat.com>
Automatic merge from submit-queue (batch tested with PRs 44119, 42538, 43802, 42336, 43396)

iSCSI CHAP support

**What this PR does / why we need it**:
To support CHAP authentication in a multi-tenant setup
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:

```release-note
Support iSCSI CHAP authentication
```
Automatic merge from submit-queue

upgrade wordpress to 4.7.3 latest

see kubernetes/kubernetes#42029

/release-note-none
Automatic merge from submit-queue

fix typos and update an outdated reference in persistent-volume-provi…

…sioning README



**What this PR does / why we need it**:

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:

```release-note
```
Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
Automatic merge from submit-queue

Fixed typos and issues in examples/volumes/glusterfs/README.md

**What this PR does / why we need it**:

This PR updates the GlusterFS `README.md` to fix several typos, outdated documentation and examples that did not work anymore.

**Which issue this PR fixes** 

None

**Special notes for your reviewer**:

None

**Release note**:

`release-note-NONE`
The docker image is nowhere to be found, so lets remove it.
There have been a request for the Dockerfile here [1], but nobody
seems to care.

redis-proxy is replaced with redis-master in test-cmd-util.sh, to
ensure that the tests still works.
The redis-proxy pod in test/fixtures/doc-yaml/user-guide/multi-pod.yaml
is replaced with valid-pod from test/fixtures/doc-yaml/admin/limitrange/valid-pod.yaml,
so redis-proxy is removed every where.

[1] kubernetes/kubernetes#4914 (comment)
Automatic merge from submit-queue

Remove redis-proxy example

The docker image is nowhere to be found, so lets remove it.
There have been a request for the Dockerfile here [1], but nobody
seems to care.


[1] kubernetes/kubernetes#4914 (comment)
----
**What this PR does / why we need it**:
This PR remove a k8s manifest which use a image which source is nowhere to be found.

```release-note
Remove redis-proxy.yaml sample, as the image is nowhere to be found.
```
Automatic merge from submit-queue (batch tested with PRs 44996, 44804)

Rearrange glusterfs artifacts to own directory.
Automatic merge from submit-queue

README.md: Update outdated links

**What this PR does / why we need it**:
the PR aims to update some links.
Some links with "#" would not redirect to right point of pages.
Other links without "#" can work, but they are outdated. I change them by the way.

**Special notes for your reviewer**:

**Release note**:

```release-note
```
none
@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label May 1, 2017
@sebgoa
Copy link
Contributor Author

sebgoa commented May 1, 2017

@k8s-bot test this

@ahmetb
Copy link
Member

ahmetb commented May 1, 2017

I'm currently -1 for moving all existing examples here. We have a chance to do a clean start and we are planning to keep only "tutorial examples" in this repository. Let’s hold off on shuffling code around until we have a clean path forward. I’ll set up a Hangouts meeting with SIG-Apps sometime this week.

@ahmetb
Copy link
Member

ahmetb commented May 12, 2017

After the discussion on https://groups.google.com/d/msgid/kubernetes-sig-apps/CACZ5N2amx9GUbXM%2BokJ%3DBB%2BWZu0scir2GWwwFguj-T43LokRVg%40mail.gmail.com?utm_medium=email&utm_source=footer I think we can move forward with this.

/lgtm

Once merged, we should probably find a way to reorganize the content in this repository and make proper redirections in the original repository (not sure about the order). Then we can evaluate each of the examples (most of them were already evaluated in my proposal) and stage each one for deletion. We can probably try to contact the owners of each example and encourage them to move things to their own repo.

@ahmetb
Copy link
Member

ahmetb commented May 12, 2017

Also, I am planning to move README.md files of maintained examples (guestbook ones, wordpress-mysql and cassandra) to the docs repository and link back here for the .yaml files. The new README.md files of these maintained examples would be just links to the k8s.io website.

Most of the stuff in volumes/ can probably moved to documentation repo as they are actually just serving documentation purposes and they are neither usable out of the box nor full examples.

@sebgoa
Copy link
Contributor Author

sebgoa commented May 19, 2017

I am closing this one right now, and I am making a fresh one shortly.
I will move everything to /staging

@tmap-cicd
Copy link

🔍 YAML Validation Results

YAML validation failed

📊 Summary: 12/13 files valid (1 failed)

📋 File Details:

cluster-dns/dns-backend-rc.yaml

cluster-dns/dns-backend-service.yaml

cluster-dns/dns-frontend-pod.yaml

cluster-dns/namespace-dev.yaml

cluster-dns/namespace-prod.yaml

cockroachdb/cockroachdb-statefulset.yaml

  • Errors:
    • Invalid YAML syntax: expected a single document in the stream
      in "", line 1, column 1:
      apiVersion: v1
      ^
      but found another document
      in "", line 22, column 1:
      ---
      ^

elasticsearch/es-rc.yaml

elasticsearch/es-svc.yaml

elasticsearch/production_cluster/es-client-rc.yaml

elasticsearch/production_cluster/es-data-rc.yaml

elasticsearch/production_cluster/es-discovery-svc.yaml

elasticsearch/production_cluster/es-master-rc.yaml

elasticsearch/production_cluster/es-svc.yaml


This comment was automatically generated by the YAML Validator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: no Indicates the PR's author has not signed the CNCF CLA.

Projects

None yet

Development

Successfully merging this pull request may close these issues.