Skip to content

Essential ystack services' test coverage using y-assert#30

Merged
solsson merged 65 commits into
masterfrom
y-assert-dogfooding
Jun 21, 2020
Merged

Essential ystack services' test coverage using y-assert#30
solsson merged 65 commits into
masterfrom
y-assert-dogfooding

Conversation

@solsson

@solsson solsson commented Jun 5, 2020

Copy link
Copy Markdown
Collaborator

No description provided.

solsson added 14 commits June 5, 2020 12:41
@solsson
CI should validate our examples, and run our specs
861590c
@solsson
A gentle reminder
e824699
@solsson
Many projects will want to tweak build or deploy for CI runs
2d4ffbd
@solsson
Oh, buildkitd had scale=0 because of a ./k3s kustomization
34b66e2
@solsson
./test.sh now runs not only examples but also y-assert, which is
9f6d6a6 
a milestone even if specs are just dummy
@solsson
Current operator, now that we depend on kubernetes-assert
7e2f839
@solsson
Cleanup
1b37e93
@solsson
Cleanup
af3ada3
@solsson
The actual specs, based on kubernetes-assert's example project
6474e06
@solsson
Now ./k3s scales both up and down :)
3b51d8a
@solsson
kubie will by design not use a kubeconfig from the previous run
9381eb7
@solsson
Uses a skaffold build of the runtime from Yolean/kubernetes-assert#15
68ada7a
@solsson
Tries to avoid a sudo rm, but not get an old kubeconfig
7a7523d
@solsson
Starts a completion definition
b458d89
@solsson solsson mentioned this pull request Jun 5, 2020
Merged
solsson added 6 commits June 5, 2020 21:31
@solsson
Fixes spec file count
962c232
@solsson
Fixed, but doesn't help, ystack-proxy gets old config
045820d
@solsson
Cleanup without sudo
0e0a890
@solsson
I thought that node name resolvable from server would fix metric errors
7ada575 
E0606 09:05:46.810522       1 available_controller.go:420] v1beta1.metrics.k8s.io failed with: failing or missing response from https://10.43.103.169:443/apis/metrics.k8s.io/v1beta1: Get https://10.43.103.169:443/apis/metrics.k8s.io/v1beta1: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

... but no, they're still there.
@solsson
See the first line of the script
df9d1c0
@solsson
Cleanup would run at unwanted occations
65d9444
@solsson
solsson force-pushed the y-assert-dogfooding branch from 2df811b to 65d9444 Compare June 6, 2020 09:33
solsson added 27 commits June 8, 2020 11:55
@solsson
Faster specs build and less boilerplate using runtime
99cd4fa
@solsson
Finally asserting stuff, but still with skaffold dev
835da10
@solsson
Still very basic specs
2cb8a7d
@solsson
Covers the essential http endpoints in ystack
843a7fc
@solsson
Merge branch 'specs-to-assert-runtime' into y-assert-dogfooding
4c5ff71
@solsson
Stay running until there's zero test failures
5d1a75f
@solsson
Adds a jq criteria to pass (i.e. exit) only if the expected metric ha…
c36b897 
…d values
@solsson
I think this is good enough for a PoC
0d4b993
@solsson
Verifies monitoring endpoints early in y-assert
3514d6d
@solsson
Runs same crane build that developers get locally
a5b9263
@solsson
Only add port number if it isn't there already
e105d11
@solsson
Includes agent in server, by commenting out
34b78d0
@solsson
This kubefwd release seems to work with Ubuntu 20.04
07ca461
@solsson
Changes container name to match our earlier terminology
b00c115
@solsson
Fixes a wrapper script mistake
503b740
@solsson
Removes agent1 node config as it will quickly get outdated
6e92746
@solsson
Merge branch 'master-container-only' into y-assert-dogfooding
4f82a19
@solsson
Having a named context helps, even when it's alone in the yaml file
555ce0e
@solsson
Another reference to master's hostname
4d4e204
@solsson
Fixes dev volume independent of CWD
2a24a23
@solsson
Scope creep y-docker-compose with some shortcuts
387faba
@solsson
These 3 places refer to a kubernetes-assert commit
bee8bde
@solsson
Allows nonroot users to modify appended files, such as assert specs
c47460e 
The chosen UID is for gcr.io/distroless nonroot, but the GID is nogroup
present in distro base images like ubuntu
@solsson
Upgrading kuberenetes-assert is now two git refs and an autobuild sha
6837874
@solsson
Support CI builds with y-build-like-sync
139effc
@solsson
Three refs to a kubernetes-assert commit, again
4ed0891
@solsson
Helps us detect y-cluster-assert-install issues
bf846d4
@solsson
solsson merged commit f231c89 into master Jun 21, 2020
@solsson

solsson commented Jun 21, 2020 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Autobuild at https://hub.docker.com/r/solsson/ystack-runner passed with build logs ending

2020-06-21T06:59:05Z Prometheus queries for test results will use labels: namespace="ystack-specs"
2020-06-21T06:59:05Z cleanup-ish: kubectl --context=default get namespace -l janitor/ttl=23h -o name | xargs kubectl --context=default delete
jq: error (at <stdin>:0): No results
jq: error (at <stdin>:0): No results
Zero failures now with: curl -s --data query=assertions_failed{namespace="ystack-specs"} http://monitoring.ystack.svc.cluster.local:9090/api/v1/query
+ '[' false = true ']'
Removing bupvk8bgjhmhquozospbscb_sut_1 ...
�[1A�[2K Removing bupvk8bgjhmhquozospbscb_sut_1 ... �[32mdone�[0m �[1BGoing to remove bupvk8bgjhmhquozospbscb_sut_1
Tests in docker-compose.test.yml succeeded
Pushing index.docker.io/solsson/ystack-runner:latest...
Done!
Build finished

Locally I've never had "Zero failures" immediately after "No results", but I guess it can happen given certain timings between run/scrape/curl.

The runner that was pushed is solsson/ystack-runner@sha256:617b86f3a9ec6e1ef9fb45c14710bd16d6e418249c6f4e9c03fd002f737a3988.

@solsson solsson mentioned this pull request Jun 21, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@solsson