kubernetes/pkg/kubectl/cmd/testdata/edit
Laszlo Janosi a6da2b1472 K8s SCTP support implementation for the first pull request
The requested Service Protocol is checked against the supported protocols of GCE Internal LB. The supported protocols are TCP and UDP.

SCTP is not supported by OpenStack LBaaS. If SCTP is requested in a Service with type=LoadBalancer, the request is rejected. Comment style is also corrected.

SCTP is not allowed for LoadBalancer Service and for HostPort. Kube-proxy can be configured not to start listening on the host port for SCTP: see the new SCTPUserSpaceNode parameter

changed the vendor github.com/nokia/sctp to github.com/ishidawataru/sctp. I.e. from now on we use the upstream version.

netexec.go compilation fixed. Various test cases fixed

SCTP related conformance tests removed. Netexec's pod definition and Dockerfile are updated to expose the new SCTP port(8082)

SCTP related e2e test cases are removed as the e2e test systems do not support SCTP

sctp related firewall config is removed from cluster/gce/util.sh. Variable name sctp_addr is corrected to sctpAddr in pkg/proxy/ipvs/proxier.go

cluster/gce/util.sh is copied from master
2018-08-27 05:56:27 +00:00
..
testcase-apply-edit-last-applied update testcase for edit 2018-07-18 15:41:38 +08:00
testcase-apply-edit-last-applied-list wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-apply-edit-last-applied-list-fail wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-apply-edit-last-applied-syntax-error wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-create-list wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-create-list-error K8s SCTP support implementation for the first pull request 2018-08-27 05:56:27 +00:00
testcase-edit-error-reedit wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-edit-from-empty forbid kubectl edit an empty list 2017-08-11 08:44:13 +08:00
testcase-edit-output-patch wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-immutable-name
testcase-list wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-list-errors K8s SCTP support implementation for the first pull request 2018-08-27 05:56:27 +00:00
testcase-list-record wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-missing-service
testcase-no-op
testcase-not-update-annotation wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-repeat-error Add advanced 'kubectl edit' test scenarios 2017-02-14 14:50:45 -05:00
testcase-schemaless-list wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-single-service wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-syntax-error wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
testcase-unknown-field-known-group-kind Fix tests to support ObjectMeta omitempty semantics 2018-08-21 13:17:25 +05:30
testcase-unknown-version-known-group-kind Fix tests to support ObjectMeta omitempty semantics 2018-08-21 13:17:25 +05:30
testcase-update-annotation wire printflags through additional cmds 2018-04-25 16:07:32 -04:00
BUILD Autogenerated: hack/update-bazel.sh 2018-02-16 13:43:01 -08:00
README
record_editor.sh Update all script to use /usr/bin/env bash in shebang 2018-04-19 13:20:13 +02:00
record_testcase.sh Update all script to use /usr/bin/env bash in shebang 2018-04-19 13:20:13 +02:00
record.go
test_editor.sh Update all script to use /usr/bin/env bash in shebang 2018-04-19 13:20:13 +02:00

This folder contains test cases for interactive edit, and helpers for recording new test cases

To record a new test:

1. Start a local cluster running unsecured on http://localhost:8080 (e.g. hack/local-up-cluster.sh)
2. Set up any pre-existing resources you want to be available on that server (namespaces, resources to edit, etc)
3. Run ./pkg/kubectl/cmd/testdata/edit/record_testcase.sh my-testcase
4. Run the desired `kubectl edit ...` command, and interact with the editor as desired until it completes.
  * You can do things that cause errors to appear in the editor (change immutable fields, fail validation, etc)
  * You can perform edit flows that invoke the editor multiple times
  * You can make out-of-band changes to the server resources that cause conflict errors to be returned
  * The API requests/responses and editor inputs/outputs are captured in your testcase folder
5. Type exit.
6. Inspect the captured requests/responses and inputs/outputs for sanity
7. Modify the generated test.yaml file:
  * Set a description of what the test is doing
  * Enter the args (if any) you invoked edit with
  * Enter the filename (if any) you invoked edit with
  * Enter the output format (if any) you invoked edit with
  * Optionally specify substrings to look for in the stdout or stderr of the edit command
8. Add your new testcase name to the list of testcases in edit_test.go
9. Run `go test ./pkg/kubectl/cmd -run TestEdit -v` to run edit tests