Update dependency kubernetes-sigs/cluster-api-provider-openstack to v0.11.3 #733
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Build succeeded (e2e-quick-test pipeline). ✔️ k8s-cluster-api-provider-e2e-quick SUCCESS in 37m 47s Warning: SCS Compliance resultsTesting SCS Compatible KaaS version v2 ******************************************************* Testing standard Kubernetes version policy ... Reference: https://raw.githubusercontent.com/SovereignCloudStack/standards/main/Standards/scs-0210-v2-k8s-version-policy.md ... INFO: Checking cluster specified by default context in /home/ubuntu/src/github.com/SovereignCloudStack/k8s-cluster-api-provider/terraform/pr733-36de57.yaml.gx-scs-zuul. INFO: The K8s cluster version 1.28.8 of cluster 'pr733-36de57-admin@pr733-36de57' is still in the recency time window.... returned 0 errors, 0 aborts Testing standard Kubernetes node distribution and availability ... Testing standard CNCF Kubernetes conformance ... Verdict for subject KaaS_V1, SCS Compatible KaaS, version v2: PASSED Testing standard Kubernetes version policy ... Testing standard Kubernetes node distribution and availability ... Verdict for subject KaaS_V1, SCS Compatible KaaS, version v1: PASSED Sonobouy results=== Collecting results === time="2024-04-17T16:46:13Z" level=info msg="delete request issued" dry-run=false kind=namespace namespace=sonobuoy time="2024-04-17T16:46:13Z" level=info msg="delete request issued" dry-run=false kind=clusterrolebindings names="[sonobuoy-serviceaccount-sonobuoy]" time="2024-04-17T16:46:13Z" level=info msg="delete request issued" dry-run=false kind=clusterroles names="[sonobuoy-serviceaccount-sonobuoy]" Plugin: e2e Status: passed Total: 7393 Passed: 5 Failed: 0 Skipped: 7388Plugin: systemd-logs Run Details: Namespace "sonobuoy" has status {Phase:Terminating Conditions:[]} Namespace "sonobuoy" has status {Phase:Terminating Conditions:[{Type:NamespaceDeletionDiscoveryFailure Status:False LastTransitionTime:2024-04-17 16:46:35 +0000 UTC Reason:ResourcesDiscovered Message:All resources successfully discovered} {Type:NamespaceDeletionGroupVersionParsingFailure Status:False LastTransitionTime:2024-04-17 16:46:35 +0000 UTC Reason:ParsedGroupVersions Message:All legacy kube types successfully parsed} {Type:NamespaceDeletionContentFailure Status:False LastTransitionTime:2024-04-17 16:46:35 +0000 UTC Reason:ContentDeleted Message:All content successfully deleted, may be waiting on finalization} {Type:NamespaceContentRemaining Status:True LastTransitionTime:2024-04-17 16:46:35 +0000 UTC Reason:SomeResourcesRemain Message:Some resources are remaining: pods. has 1 resource instances} {Type:NamespaceFinalizersRemaining Status:False LastTransitionTime:2024-04-17 16:46:35 +0000 UTC Reason:ContentHasNoFinalizers Message:All content-preserving finalizers finished}]} Namespace "sonobuoy" has been deleted Deleted all ClusterRoles and ClusterRoleBindings. |
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
97d3d4e to
eafee88
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
eafee88 to
665ab51
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
665ab51 to
784dd41
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
3 times, most recently
from
95a73a7 to
ece5d5d
Compare
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
ece5d5d to
6d265dc
Compare
|
Build failed (e2e-quick-test pipeline). ❌ k8s-cluster-api-provider-e2e-quick FAILURE in 42m 21s |
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
6d265dc to
35bf15c
Compare
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
35bf15c to
4d6b775
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
4d6b775 to
116a754
Compare
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
116a754 to
6726a0e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
6726a0e to
c8f9fab
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
c8f9fab to
04deaf7
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
04deaf7 to
2461ae7
Compare
renovate
bot
changed the title
…0.11.3 Signed-off-by: SCS Renovate Bot <renovatebot@scs.community>
renovate
bot
force-pushed
the
renovate/kubernetes-sigs-cluster-api-provider-openstack-0.x
branch
from
2461ae7 to
3eb8b9e
Compare
renovate
bot
changed the title
This PR contains the following updates:
0.9.0->0.11.3Release Notes
kubernetes-sigs/cluster-api-provider-openstack (kubernetes-sigs/cluster-api-provider-openstack)
v0.11.3Compare Source
Changes since v0.11.2
🐛 Bug Fixes
🌱 Others
Thanks to all our contributors! 😊
v0.11.2Compare Source
Changes since v0.11.1
🐛 Bug Fixes
🌱 Others
Thanks to all our contributors! 😊
v0.11.1Compare Source
IMPORTANT
This release contains an important fix for a bug which prevented security groups from being correctly applied to ports when creating a new server. We recommend all users should upgrade to this new release. Note that the fix will not be applied to any existing Machines which were created by v0.11.0. To correctly apply security groups to these Machines you should delete them and allow them to be reprovisioned.
Changes since v0.11.0
🐛 Bug Fixes
OpenStackMachine.Spec.SecurityGroups(#2239)🌱 Others
Thanks to all our contributors! 😊
v0.11.0Compare Source
✨ New Features
🐛 Bug Fixes
OpenStackMachineto use their ownIdentityRef(#2191)🌱 Others
📖 Additionally, there have been 7 contributions to our documentation and book. (#2168, #2125, #2123, #2120, #2100, #1565, #2032)
Thanks to all our contributors! 😊
v0.10.7Compare Source
Changes since v0.10.6
🐛 Bug Fixes
Thanks to all our contributors! 😊
v0.10.6Compare Source
Changes since v0.10.5
🐛 Bug Fixes
🌱 Others
Thanks to all our contributors! 😊
v0.10.5Compare Source
Changes since v0.10.4
🐛 Bug Fixes
Thanks to all our contributors! 😊
v0.10.4Compare Source
Changes since v0.10.3
🐛 Bug Fixes
🌱 Others
Thanks to all our contributors! 😊
v0.10.3Compare Source
Changes since v0.10.2
🐛 Bug Fixes
🌱 Others
Thanks to all our contributors! 😊
v0.10.2Compare Source
What's Changed
Full Changelog: kubernetes-sigs/cluster-api-provider-openstack@v0.10.1...v0.10.2
v0.10.1Compare Source
What's Changed
Full Changelog: kubernetes-sigs/cluster-api-provider-openstack@v0.10.0...v0.10.1
v0.10.0Compare Source
Breaking API Changes
v0.10.0 is a major update which brings major changes to the API.
v1alpha5 is no longer served
If you are still using v1alpha5, this will not work in v0.10.0. However, for this release only objects are still defined in the CRDs and the code is still present, so as a temporary workaround it is possible to manually edit the CRDs to set versions.served to true for v1alpha5 objects. This is not tested, and we have low confidence that this will work without problems. Some manual effort may be required to check and fix automatically converted objects.
v1alpha6 and v1alpha7 are deprecated
v1alpha6 and v1alpha7 objects will be automatically converted to v1beta during use. This is well tested. We don’t anticipate problems with these conversions.
We will stop serving and testing v1alpha6 in the next release.
v1alpha7 is not marked deprecated in v0.10.0 to allow a switch-over period without deprecation warnings, but will be marked deprecated in the next release. Will will stop serving and testing it in a release after that.
You should update to use v1beta1 natively as soon as possible.
v1beta1 is released
v1beta1 marks a major update to the CAPO API. The specific changes from v1alpha7 are documented here: https://cluster-api-openstack.sigs.k8s.io/topics/crd-changes/v1alpha7-to-v1beta1
More than this, though, it marks an intention by the maintainers to stop making breaking changes. The API will continue to evolve, but we will make every effort to do this without introducing more backwards-incompatible changes.
Removal of hardcoded Calico CNI security group rules
This is documented more completely in the API upgrade documentation.
Prior to v1beta1, when using managed security groups we would automatically add certain rules which were specific to Calico CNI. It was not possible to add rules for any other CNI. A common way to work round this was to set
allowAllInClusterTraffic: true.With v1beta1 there are no longer any implicit rules for any CNI. However, it is now possible to specify custom rules in the cluster spec which will be automatically added to managed security groups. Users of Calico CNI must now add these rules explicitly. Users of other CNIs now have the option of using managed security groups.
Calico CNI rules will be added automatically when upgrading to v1beta1 from a previous API version.
The Calico CNI rules have been added to the release templates, so for now creating a cluster with clusterctl will continue to have Calico rules when using the default templates.
Management cluster changes
Removal of MutatingWebhookConfiguration
CAPO no longer uses a mutating webhook, and its configuration is removed. If you upgrade your management cluster with clusterctl this will be handled correctly. If you do it manually you must ensure you remove the MutatingWebhookConfiguration
capo-mutating-webhook-configuration. If you do not you may see errors like the one in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/1927.Minimum management cluster version is now 1.25
v0.10.0 now uses https://kubernetes.io/docs/reference/using-api/cel/ for some API validations, which only became available without a feature gate in 1.25. Consequently we now require the management cluster to be at least k8s 1.25.
Highlighted new features
API Reference documentation
We now automatically publish API reference documentation! The documentation for v1beta1 can be found here: https://cluster-api-openstack.sigs.k8s.io/api/v1beta1/api
Floating IP IPAM Provider
It is now possible to allocate floating IPs for individual machines using the new Floating IP IPAM Provider documented here: https://cluster-api-openstack.sigs.k8s.io/api/v1alpha1/api#infrastructure.cluster.x-k8s.io/v1alpha1.OpenStackFloatingIPPool
Attach them to a machine via the new floatingIPPoolRef in OpenStackMachineSpec: https://cluster-api-openstack.sigs.k8s.io/api/v1beta1/api#infrastructure.cluster.x-k8s.io/v1beta1.OpenStackMachineSpec
What's Changed
New Features
flatcar-sysexttemplate to use regular Flatcar images by @tormath1 in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/1776allocation_poolsfor subnet by @dulek in https://github.com/kubernetes-sigs/cluster-api-provider-Bug fixes
Documentation
Administrative
openstack/pull/1836
API changes
spec.allowAllInClusterTraffictospec.ManagedSecurityGroupsby @EmilienM in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/1892IdentityRef.Kindby @EmilienM in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/1903openstack/pull/1847
v1alpha8tov1beta1by @EmilienM in https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/1902Changes to build, test, and CI, minor changes, and code tidy ups
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.