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
1. What kops version are you running? The command kops version, will display
this information.
v1.30.0
3. What cloud provider are you using?
AWS 4. What commands did you run? What is the simplest way to reproduce this issue?
I found #16818 so the issue was already reproduced.
9. Anything else do we need to know?
if I use master branch and build Kops, the issue does not occur in 1.30.0-beta.1
I tried setting KOPS_STATE_S3_ACL=private which solves the empty acl, but there is no way to overwrite server_side_encryption.
When is the next release published from master?
The text was updated successfully, but these errors were encountered:
I opened a cherrypick for 1.30 #16830 so this will be included in the next 1.30.2 release. We just created the 1.30.1 release so 1.30.2 may be a week or two away.
/kind bug
I am upgrading from Kops 1.29.0 to 1.30.0 and facing the issue described in #16818
1. What
kops
version are you running? The commandkops version
, will displaythis information.
v1.30.0
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
I found #16818 so the issue was already reproduced.
9. Anything else do we need to know?
if I use master branch and build Kops, the issue does not occur in 1.30.0-beta.1
I tried setting
KOPS_STATE_S3_ACL=private
which solves the emptyacl
, but there is no way to overwriteserver_side_encryption
.When is the next release published from master?
The text was updated successfully, but these errors were encountered: