Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
a7364c08
Commit
a7364c08
authored
Jul 13, 2015
by
Tim Hockin
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #10994 from erictune/conformance_master
Conformance test update
parents
69b5b2c2
2459cfa9
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
44 additions
and
39 deletions
+44
-39
conformance-test.sh
hack/conformance-test.sh
+36
-32
ginkgo-e2e.sh
hack/ginkgo-e2e.sh
+8
-7
No files found.
hack/conformance-test.sh
View file @
a7364c08
...
...
@@ -14,6 +14,31 @@
# See the License for the specific language governing permissions and
# limitations under the License.
# When run as described below, the conformance test tests whether a cluster
# supports key features for Kubernetes version 1.0.
# Instructions:
# - Setup a Kubernetes cluster with $NUM_MINIONS nodes (defined below).
# - Provide a Kubeconfig file whose current context is set to the
# cluster to be tested, and with suitable auth setting.
# - Specify the location of that kubeconfig with, e.g.:
# declare -x KUBECONFIG="$HOME/.kube/config"
# - Specify the location of the master with, e.g.:
# declare -x KUBE_MASTER_IP="1.2.3.4"
# - Make sure only essential pods are running and there are no failed/pending pods.
# - Go to a git tree that contains the kubernetes source.
# - git clone git://github.com/GoogleCloudPlatform/kubernetes.git
# - Checkout the upstream/conformance-test-v1 branch
# - git checkout upstream/conformance-test-v1
# - The working tree will be in a "detached HEAD" state.
# - Make binaries needed by e2e
# make clean
# make quick-release
# - Run the test and capture output:
# hack/conformance-test.sh 2>&1 | tee conformance.$(date +%FT%T%z).log
#
# About the conformance test:
# The conformance test checks whether a kubernetes cluster supports
# a minimum set of features to be called "Kubernetes". It is similar
# to `hack/e2e-test.sh` but it differs in that:
...
...
@@ -31,40 +56,13 @@
# - tests of optional features, such as volume types.
# - tests of performance, scale, or reliability
# - known flaky tests.
# The conformance test should be run from a github repository at
# commit TBDCOMMITNUMBER. Otherwise, it may not include the right
# set of tests.
# e.g.:
# cd /new/directory
# git clone git://github.com/GoogleCloudPlatform/kubernetes.git
# cd kubernetes
# git checkout TBDCOMMITNUMBER.
# The working tree will be in a "detached HEAD" state.
#
# When run as described above, the conformance test tests whether a cluster is
# supports key features for Kubernetes version 1.0.
#
# TODO: when preparing to release a new major or minor version of Kubernetes,
# then update above commit number, reevaluate the set of e2e tests,
# create a new conformance-test-vX.Y branch, update mentions of that branch in this file,
# reevaluate the set of e2e tests,
# update documentation at docs/getting-started-guides/README.md to have
# a new column for conformance at that new version, and notify
# community.
# Instructions:
# - Setup a Kubernetes cluster with $NUM_MINIONS nodes (defined below).
# - Provide a Kubeconfig file whose current context is set to the
# cluster to be tested, and with suitable auth setting.
# - Specify the location of that kubeconfig with, e.g.:
# declare -x KUBECONFIG="$HOME/.kube/config"
# - Specify the location of the master with, e.g.:
# declare -x KUBE_MASTER_IP="1.2.3.4"
# - Make sure only essential pods are running and there are no failed/pending pods.
# - Make binaries needed by e2e, e.g.:
# make clean
# make quick-release
# - Run the test and capture output:
# hack/conformance-test.sh 2>&1 | tee conformance.$(date +%FT%T%z).log
:
${
KUBECONFIG
:?
"Must set KUBECONFIG before running conformance test."
}
:
${
KUBE_MASTER_IP
:?
"Must set KUBE_MASTER_IP before running conformance test."
}
...
...
@@ -98,13 +96,19 @@ echo "Conformance test checking conformance with Kubernetes version 1.0"
# Restart: node management.
# Scale: performance
# Services.*load balancer: not all cloud providers have a load balancer.
# Services.*NodePort: flaky
# Services.*NodePort: requires you to open the firewall yourself, so not covered.
# Services.*nodeport: requires you to open the firewall yourself, so not covered.
# Shell: replies on optional ssh access to nodes.
# SSH: optional feature.
# Addon\supdate: requires SSH
# Volumes: contained only skipped tests.
export
CONFORMANCE_TEST_SKIP_REGEX
=
"Cadvisor|MasterCerts|Density|Cluster
\s
level
\s
logging.*|Etcd
\s
failure.*|Load
\s
Capacity|Monitoring|Namespaces.*seconds|Pod
\s
disks|Reboot|Restart|Nodes|Scale|Services.*load
\s
balancer|Services.*NodePort|Shell|SSH|Volumes"
# Clean\sup\spods\son\snode: performance
# MaxPods\slimit\snumber\sof\spods: not sure why this wasn't working on GCE but it wasn't.
# Kubectl\sclient\sSimple\spod: not sure why this wasn't working on GCE but it wasn't
# DNS: not sure why this wasn't working on GCE but it wasn't
export
CONFORMANCE_TEST_SKIP_REGEX
=
"Cadvisor|MasterCerts|Density|Cluster
\s
level
\s
logging|Etcd
\s
failure|Load
\s
Capacity|Monitoring|Namespaces.*seconds|Pod
\s
disks|Reboot|Restart|Nodes|Scale|Services.*load
\s
balancer|Services.*NodePort|Services.*nodeport|Shell|SSH|Addon
\s
update|Volumes|Clean
\s
up
\s
pods
\s
on
\s
node|Skipped|skipped|MaxPods
\s
limit
\s
number
\s
of
\s
pods|Kubectl
\s
client
\s
Simple
\s
pod|DNS"
declare
-x
KUBERNETES_CONFORMANCE_TEST
=
"
1
"
declare
-x
KUBERNETES_CONFORMANCE_TEST
=
"
y
"
declare
-x
NUM_MINIONS
=
4
hack/ginkgo-e2e.sh
exit
$?
hack/ginkgo-e2e.sh
View file @
a7364c08
...
...
@@ -44,10 +44,10 @@ source "${KUBE_ROOT}/cluster/kube-env.sh"
# ---- Do cloud-provider-specific setup
if
[[
-n
"
${
KUBERNETES_CONFORMANCE_TEST
:-}
"
]]
;
then
echo
"Conformance test: not doing test setup."
KUBERNETES_PROVIDER
=
""
auth_config
=(
"--kubeconfig=
${
KUBECONFIG
}
"
)
KUBERNETES_PROVIDER
=
""
auth_config
=(
"--kubeconfig=
${
KUBECONFIG
}
"
)
else
echo
"Setting up for KUBERNETES_PROVIDER=
\"
${
KUBERNETES_PROVIDER
}
\"
."
...
...
@@ -58,7 +58,7 @@ else
detect-master
>
/dev/null
auth_config
=(
"--kubeconfig=
${
KUBECONFIG
:-
$DEFAULT_KUBECONFIG
}
"
"--kubeconfig=
${
KUBECONFIG
:-
$DEFAULT_KUBECONFIG
}
"
)
fi
...
...
@@ -73,8 +73,9 @@ if [[ "${KUBERNETES_PROVIDER}" == "gke" ]]; then
fi
ginkgo_args
=()
if
[[
-n
${
CONFORMANCE_TEST_SKIP_REGEX
:-}
]]
;
then
ginkgo_args+
=(
"--skip=
\"
${
CONFORMANCE_TEST_SKIP_REGEX
}
\"
"
)
if
[[
-n
"
${
CONFORMANCE_TEST_SKIP_REGEX
:-}
"
]]
;
then
ginkgo_args+
=(
"--skip=
${
CONFORMANCE_TEST_SKIP_REGEX
}
"
)
ginkgo_args+
=(
"--seed=1436380640"
)
fi
if
[[
${
GINKGO_PARALLEL
}
=
~ ^[yY]
$
]]
;
then
ginkgo_args+
=(
"-p"
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment