This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates project schema to Kubebuilder v3 compliant schema. Following changes have been performed:
PROJECT
file is now Kubebuilder v3 compliantapi/v1alpha1
examples
folder has been moved toconfig/samples
to follow Kubebuilder v3 scaffoldingMakefile
has been revamped - addedhelp
, reshuffled command order, updatedtest
target to use newsetup-env
binary (could also be used for Resolve Latest Controller Runtime Envtest Failures contour#3832)Kustomize
templating based on Kubebuilder scaffolding.namePrefix
is not used, since it changes deployment name tocontour-operator-contour-operator
, which breakstest/e2e/operator_test.go
(same string used for deployment name and container name). If wanted, we can sort this out as well.nonroot
to UID65532
(default by Kubebuilder)controller-runtime
update fromv0.9.0-beta0
tov0.9.2
There are quite some minor tweaks, mostly to naming conventions, so it would be great if someone else can take a look as well and provide some feedback what we want to keep "the old way" and what in "kubebuilder v3" way.
Regarding failing
test-e2e
:latest
tag still includesnonroot
user and since new deployment includes parametersecurityContext.allowPrivilegeEscalation: false
, it fails on deployinglatest
version. AswaitForImage
is waiting for all pods with labelcontrol-plane: contour-operator
to have latest image, it reaches timeout (old pod is never terminated, as deletion is not triggered, since loop is waiting for new pod to become available).Updates: #392
cc: @danehans @youngnick
Signed-off-by: Bostjan Bozic [email protected]