Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.7 backports 2020-09-03 #13065

Merged
merged 5 commits into from Sep 4, 2020
Merged

v1.7 backports 2020-09-03 #13065

merged 5 commits into from Sep 4, 2020

Conversation

borkmann
Copy link
Member

@borkmann borkmann commented Sep 3, 2020

v1.7 backports 2020-09-03

Once this PR is merged, you can update the PR labels via:

$ for pr in 13003 10576 12884; do contrib/backporting/set-labels.py $pr done 1.7; done

@borkmann borkmann added release-note/misc This PR makes changes that have no direct user impact. backport/1.7 labels Sep 3, 2020
@borkmann borkmann requested a review from a team as a code owner September 3, 2020 08:07
@maintainer-s-little-helper maintainer-s-little-helper bot added the kind/backports This PR provides functionality previously merged into master. label Sep 3, 2020
@borkmann
Copy link
Member Author

borkmann commented Sep 3, 2020

test-backport-1.7

Copy link
Member

@pchaigno pchaigno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small change required below. Without that the GuestBook test will fail.

role: slave
app: redis
role: follower
tier: backend
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as for the v1.8 backport: the frontend image below will need to be updated to match the Docker image version used in master:

-         image: gcr.io/google-samples/gb-frontend:v4
+         image: gcr.io/google-samples/gb-frontend:v6

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the hint, I just repushed

@borkmann
Copy link
Member Author

borkmann commented Sep 3, 2020

test-backport-1.7

Copy link
Member

@pchaigno pchaigno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 for my changes

@kkourt
Copy link
Contributor

kkourt commented Sep 4, 2020

https://jenkins.cilium.io/job/Cilium-PR-Doc-Tests/2407/console:

10:22:50  (sphinx-build -b spelling -d "_build/doctrees" "." "_build/spelling" -q -E  2>&1 && touch check-build.ok) > _build/warnings.txt
10:23:09  Please fix the following documentation warnings:
10:23:09  gettingstarted/k8s-install-connectivity-test.rst <included from /srv/Documentation/gettingstarted/k8s-install-kubespray.rst>:1: WARNING: Title level inconsistent:
10:23:09  
10:23:09  Deploy the connectivity test
10:23:09  ----------------------------
10:23:09  make: *** [Makefile:60: check-build] Error 1
10:23:09  Makefile:424: recipe for target 'test-docs' failed
10:23:09  make: *** [test-docs] Error 2

@pchaigno pchaigno self-assigned this Sep 4, 2020
pchaigno and others added 5 commits September 4, 2020 11:47
[ upstream commit 8aba1c1 ]

ae9e4be updated the GuestBook images and labels, but failed to make the
same label update in the test itself. Thus, since then, we have not been
running any connectivity check in the GuestBook test. That went
unnoticed because we didn't check that the set of pods returned (from
which we run connectivity checks) was not empty.

This commit fixes it by:
1. Updating the label in the test itself to app=guestbook.
2. Adding a check that the set of pods selected isn't empty.

However, the nc utility we were using to check connectivity from the
frontend pods to the Redis backend isn't available in the new images.
Therefore, we also need to:
3. Use curl instead inside the frontend pods to check that the PHP
   frontend works as expected and is able to contact the Redis backend.

That's it? No. Turns out some of the pod labels and names have also been
hardcoded in the Docker images and have been updated (mostly to use more
neutral terms).
4. Update the YAML file to better match [1]. We however can't update the
   'redis-master' name because our v6 frontend image has it hardcoded. The
   v5 frontend image at [1] has 'redis-leader' as the name, but somehow
   not the v6. We want to use the v6 image because it is a lot bigger
   (cf. dffb450).
5. And finally, Bob's our uncle!

1 - https://cloud.google.com/kubernetes-engine/docs/tutorials/guestbook
Fixes: #12994
Fixes: ae9e4be ("test: replace guestbook test docker image")
Signed-off-by: Paul Chaignon <paul@cilium.io>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
[ upstream commit e166ae0 ]

Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
[ upstream commit 5d9139f ]

Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
Signed-off-by: Paul Chaignon <paul@cilium.io>
[ upstream commit beb401b ]

Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
[ upstream commit 06dbc52 ]

Removes references to things like CoreOS and old etcd versions.
Also added some further reading links for those who want to configure
cilium on kops further.

Signed-off-by: Ole Markus With <o.with@sportradar.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
@pchaigno
Copy link
Member

pchaigno commented Sep 4, 2020

test-backport-1.7
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/19908/
Five failures. Very likely unrelated to the changes in this backport PR since changes only touch documentation and one e2e test that is passing.

Suite-k8s-1.17.K8sDatapathConfig ManagedEtcd Check connectivity with managed etcd
Suite-k8s-1.17.K8sFQDNTest Restart Cilium validate that FQDN is still working
Suite-k8s-1.17.K8sIstioTest Istio Bookinfo Demo Tests bookinfo inter-service connectivity
Suite-k8s-1.17.K8sServicesTest Bookinfo Demo Tests bookinfo demo
Suite-runtime.RuntimePrivilegedUnitTests Run Tests

@pchaigno
Copy link
Member

pchaigno commented Sep 4, 2020

test-backport-1.7

@pchaigno pchaigno added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Sep 4, 2020
@nathanjsweet nathanjsweet merged commit 8c62494 into v1.7 Sep 4, 2020
@nathanjsweet nathanjsweet deleted the pr/v1.7-backports-2020-09-03 branch September 4, 2020 21:31
@pchaigno pchaigno removed their assignment Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/backports This PR provides functionality previously merged into master. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants