You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem I have: a module path and package was changed
When I try to upgrade to go v1.23.0, I have an issue with an import located in the /tools.go file.
go mod tidy
go: finding module for package k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1
go: github.com/ThalesGroup/k8s-kms-plugin imports
k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1: module k8s.io/apiserver@latest found (v0.31.3), but does not contain package k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1
Before I update to go v1.23.0: go 1.21.6 was used and k8s.io/apiserver v0.19.2 ; see go.mod
We need to figure out what to do with this module. It seems k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1 was used to store protobuf files that was generated.
From this following commit kubernetes/apiserver@c027ae3, it looks like protobuf files were moved from k8s.io/apiserver/pkg/storage/value/encrypt/envelope/ to k8s.io/kms/apis/v2alpha1 and were deleted from k8s.io/apiserver/pkg/storage/value/encrypt/envelope/:
Check the k8s.io/kms package: https://pkg.go.dev/k8s.io/[email protected]/apis/v1beta1 ; pay attention to deprecation message : Deprecated: KMSv1 is deprecated in v1.28 and will only receive security updates going forward. Use KMSv2 instead.
The text was updated successfully, but these errors were encountered:
Is it enough to rename func (p *P11) Version(ctx context.Context[...] to func (p *P11) Status(ctx context.Context[...] ? Or do we need to implement a new method Status ?
Begin replacement of github.com/ThalesGroup/k8s-kms-plugin/apis/k8s/v1beta1 with k8s.io/kms/apis/v2. However, there are other modification to do in order to update the lib with k8s.io/kms/apis/v2. Indeed, there are both changes from v1beta1 and v2, as well as github.com/ThalesGroup/k8s-kms-plugin/apis/k8s/v1beta1 which has a custom forked implementation of the lib. See #40 (comment)
Don't forget to fix TODOs
Signed-off-by: Nicolas-Peiffer <[email protected]>
What I want to achieve: update to
go v1.23.0
Problem I have: a module path and package was changed
When I try to upgrade to go v1.23.0, I have an issue with an import located in the
/tools.go
file.Before I update to go v1.23.0:
go 1.21.6
was used andk8s.io/apiserver v0.19.2
; see go.modBefore I update to go v1.23.0: the content of tools.go imported a module
"k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1"
k8s.io/apiserver v0.19.2
has indeed a module"k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1" )
. See:Latest version of where
k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1
is available isk8s.io/apiserver: v0.25.16
See:
After
k8s.io/apiserver v0.25.16
, this modulek8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1
does not exist anymore.Deletion of files appeared between v0.26.0-alpha.1 and v0.26.0-alpha.2.
We need to figure out what to do with this module. It seems
k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1
was used to store protobuf files that was generated.From this following commit kubernetes/apiserver@c027ae3, it looks like protobuf files were moved from
k8s.io/apiserver/pkg/storage/value/encrypt/envelope/
tok8s.io/kms/apis/v2alpha1
and were deleted fromk8s.io/apiserver/pkg/storage/value/encrypt/envelope/
:pkg/storage/value/encrypt/envelope/testing/v1beta1/kms_plugin_mock.go
kmsapi "k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1"
kmsapi "k8s.io/kms/apis/v1beta1"
pkg/storage/value/encrypt/envelope/testing/v2alpha1/kms_plugin_mock.go
kmsapi "k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v2alpha1"
kmsapi "k8s.io/kms/apis/v2alpha1"
Check the
k8s.io/kms
package: https://pkg.go.dev/k8s.io/[email protected]/apis/v1beta1 ; pay attention to deprecation message : Deprecated: KMSv1 is deprecated in v1.28 and will only receive security updates going forward. Use KMSv2 instead.The text was updated successfully, but these errors were encountered: