- 10 Apr, 2024 18 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
Non-timeout network errors are not fatal when an instance is deleted, for the same reasons given for removing a haproxy instance in the prior commit. It is also not fatal if the admin Secret is missing when we remove a varnish instance, or when setting its config to the NotReady VCL. Similar to reasons given for haproxy in prior commits -- in such cases we assume that Secret has been deleted in an undeployment operation, so its not necessary to set a "not configured" state, since the instance will be removed imminently.
-
Geoff Simmons authored
While here, make sure that dataplane transactions get deleted, including after errors.
-
Geoff Simmons authored
-
Geoff Simmons authored
We assume that haproxy has been stopped (and the Pod may have been deleted). Go's "permanent network error" is now deprecated, so we limit this distinction to timeout errors.
-
Geoff Simmons authored
We assume that the Service is being deleted, and delete Secret has already been executed; then it is not necessary to re-configure the offloader, since it wil be deleted altogether.
-
Geoff Simmons authored
Delay for a bit after deployment, to make sure that haproxy re-configuration/restart is complete before verifying the test.
-
Geoff Simmons authored
The test needs haproxy on the path, otherwise it's skipped.
-
Geoff Simmons authored
That is, if the varnish controller has stored no instances in its own data structures.
-
Geoff Simmons authored
We try to set the admin Secret prior to the update operation, but Incomplete or Recoverable errors setting the Secret may be resolved by the full update. So only fail the update on Fatal errors. Encapsulate setting the admin Secret for a viking Service in a common function.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
Installed from pkg.uplex.de.
-
Geoff Simmons authored
-
Geoff Simmons authored
Call helm uninstall with --wait, and where necessary, wait for viking service pods to be undeployed. This minimizes errors during the sequential e2e test run -- the controller may still be working on deletion of the resources of the previous test when resources of the next test are added.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 22 Mar, 2024 5 commits
-
-
Nils Goroll authored
Did I mention that I have always been bad with packaging stuff? Really sorry
🙇 -
Nils Goroll authored
This reverts commit 88445180.
-
Nils Goroll authored
-
Nils Goroll authored
-
Geoff Simmons authored
-
- 15 Feb, 2024 1 commit
-
-
Nils Goroll authored
-
- 30 Jan, 2024 1 commit
-
-
Nils Goroll authored
-
- 11 Jan, 2024 8 commits
-
-
Nils Goroll authored
debian has 1.2.0-1 and our fix was a67c601b0ca4bb1d605164746a929ec74cdc8ebb
-
Nils Goroll authored
-
Nils Goroll authored
master is not correct when we build a tag - I was getting a build based on an older image.
-
Nils Goroll authored
-
Nils Goroll authored
-
-
Nils Goroll authored
-
Nils Goroll authored
-
- 03 Jan, 2024 3 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 07 Dec, 2023 2 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
The base image is now debian slim 12.2 (bookworm), and haproxy is version 2.6.12. This requires seom additional CLI arguments in the dataplaneapi invocation.
-
- 04 Dec, 2023 1 commit
-
-
Geoff Simmons authored
-
- 01 Dec, 2023 1 commit
-
-
Geoff Simmons authored
-