-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Bumping envtest to 1.24 #5835
Bumping envtest to 1.24 #5835
Conversation
Changelog is missing. Please add it. |
b27a74b
to
87e633f
Compare
this need wait we bump k8s 1.24 on SDK |
87e633f
to
5ac8fe7
Compare
c4fe852
to
8f6048a
Compare
Signed-off-by: Venkat Ramaraju <[email protected]>
8f6048a
to
c90a728
Compare
/hold cancel |
Makefile
Outdated
export K8S_VERSION = 1.23 | ||
# TODO: bump this to 1.21, after kubectl `--generator` flag is removed from e2e tests. | ||
export ENVTEST_K8S_VERSION = 1.23.1 | ||
export K8S_VERSION = 1.24 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we check here if the kubebuilder tools 1.24.1 is download after the change?
Note that ENVTEST_K8S_VERSION probably is used here to get the kubebuilder-tolls, see: https://storage.googleapis.com/kubebuilder-tools
That is probably the reason for the CI be falling.
It is a block for the release so could we just revert the changes and do the bumps?
K8S_VERSION = 1.24
export ENVTEST_K8S_VERSION = 1.24.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, envtest needs a patch version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Modifying K8S_VERSION
to 1.24.1 should solve the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case it doesn't and if its taking time to debug we could just revert as @camilamacedo86 said, but I'm pretty sure changing it to 1.24.1 would make tests to pass.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@VenkatRamaraju What @varshaprasad96 is saying is correct. I think we could either set K8S_VERSION
to 1.24.0
or 1.24.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
K8S_VERSION isn't used by the ENVTEST variable. They are separate AFAIK.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind. I see we are getting rid of the specific ENV_TEST variable
@VenkatRamaraju this should be unblocked and likely needs a rebase |
Signed-off-by: Venkat Ramaraju <[email protected]>
So 1.24.1 does exist and it should work
|
@VenkatRamaraju doing some extra looking it seems like we will need to update Kind to be v0.14.0 instead of v0.11.0. In the release notes for Kind v0.13.0:
|
Signed-off-by: Venkat Ramaraju <[email protected]>
@VenkatRamaraju According to the Kubernetes 1.24 Changelog it looks like ServiceAccounts no longer have a Token Secret auto generated. Bullet Point 3:
|
Signed-off-by: Bryce Palmer <[email protected]>
Signed-off-by: Bryce Palmer <[email protected]>
Signed-off-by: Bryce Palmer <[email protected]>
@@ -244,6 +245,15 @@ var _ = Describe("Running ansible projects", func() { | |||
} | |||
Eventually(verifyMemcachedPatch, time.Minute, time.Second).Should(Succeed()) | |||
|
|||
// As of Kubernetes 1.24 a ServiceAccount no longer has a ServiceAccount token secret autogenerated. We have to create it manually here | |||
By("Creating the ServiceAccount token") | |||
secretFile, err := common.GetSASecret(tc.Kubectl.ServiceAccount, tc.Dir) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice work @everettraven 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, thanks @everettraven!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Great work!
No description provided.