OCPBUGS-34137, OCPBUGS-34460, OCPBUGS-34113, OCPBUGS-35462: sync upstream on release-1.30/go1.22 #287
Conversation
Seems like in 1.29 there are issues with cri-dockerd. There's no reason to use Docker anymore and this commit makes sure k3s uses containerd.
This commit makes sure we're fetching and putting the logs of the DevStack services as well as k3s into the artifacts for every CI job.
PR kubernetes#2468 used an incorrect condition when updating the listener timeout values and only updates them when listener's allowedCIDRs are updated. This commit fixes this by making sure timeout values are checked too.
* Add support to only run selected CSI services of the cinder CSI driver * Add support to only run selected CSI services of the manila CSI driver * Clean up source files to successfully complete linting * Update description of the `nodeid` command line parameter * Update documentation for the CSI service parameters This commit updates the documentation for the CSI controller and node service providing parameters.
The test image was recently changed and now ships with go1.22rc2. We need to use a version of golangci-lint that is compatible with it.
…rnetes#2480) Signed-off-by: Sebastian-RG <fullmetalliferous@gmail.com>
* fix: add missing labels to resources otherwise upgrades fail with `resource already exists, add missing labels` * chore: bump version
…or specify an existing floating IP (kubernetes#2166) * Add annotation to keep floationIP * Add annotation to specify floating ip to use on LB when creating ingress * Add doc for octavia.ingress.kubernetes.io/keep-floatingip & octavia.ingress.kubernetes.io/floatingip annotations * Remove debug logs * Change annotation syntax, don't create a new FIP, if user requested a particular one, add additional check if FIP already binded to correct port, add ability to update FIP of an existing ingress by updating annotation * Add missing else * Log format * Create fonctions to attach/detach fips to port * Fix bug when no fip provided in annotation the lb was created in private mode and improve openstack neutron fip logic
`subnet-id` is cumbersome to use in dual-stack environments, this commit documents that.
KMS v1 API is deprecated and in v1.29 core K8s won't allow it with default feature gates set. This commit makes sure we're proposing configuration of v2 API in example EncryptionConfigs.
In OpenStack IPv6 that uses GUAs don't require NAT to access the outside world, so IPv6 can be rechable without Floating IPs, which makes the enforcement of IPv6 LB as internal in CPO not necessary. This commit removes this enforcement, which results in IPv6 load-balancers being allowed to be shared between Services. Also, now it's possible to make the load-balancer use the IPv6 stateful address defined in the loadBalancerIP of the Service.
* magnum-auto-healer: Stop registering klog options Per [1], this is no longer desirable. We are already registering the minimal options that the KEP suggests so we can simply stop registering the others. [1] https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2845-deprecate-klog-specific-flags-in-k8s-components Signed-off-by: Stephen Finucane <stephenfin@redhat.com> * client-keystone-auth: Stop registering klog options As with magnum-auto-healer, we don't need/want to do this anymore. Don't. Signed-off-by: Stephen Finucane <stephenfin@redhat.com> * cinder-csi-plugin: Use binary name in help page Signed-off-by: Stephen Finucane <stephenfin@redhat.com> * client-keystone-auth: Migrate to cobra This one is relatively trivial since the 'Run' function in 'k8s.io/component-base/cli' does most of the heavy lifting for us now, including registering logging arguments. Signed-off-by: Stephen Finucane <stephenfin@redhat.com> * k8s-keystone-auth: Migrate to cobra This one is slightly trickier due to how we're doing configuration but there's still nothing crazy confusing here. Signed-off-by: Stephen Finucane <stephenfin@redhat.com> * occm: Remove unnecessary flag handling code k8s.io/cloud-provider switched to cobra some time back [1] and cobra uses 'pflag' rather than 'flag' under the hood. As such, there's no reason to keep the handling code for 'flag' options around. Remove it. [1] https://github.com/kubernetes/cloud-provider/blob/v0.28.0/app/controllermanager.go#L87-L124 Signed-off-by: Stephen Finucane <stephenfin@redhat.com> * occm: Register additional options correctly The 'NewCloudControllerManagerCommand' function, which generates the cobra Command that forms the basis of a cloud provider binary, accepts an 'additionalFlags' argument that allows us to (surprise) pass in additional provider-specific arguments. We were not making use of this, which means our options were not showing in the usage string shown on e.g. '--help'. Correct this on our end, while we wait for the fix in k8s.io/cloud-provider [1] to close the loop fully. In additional, move our 'InitLogs' call higher up the function to before our first logging call so that everything is initialised correctly. [1] kubernetes/kubernetes#120522 Signed-off-by: Stephen Finucane <stephenfin@redhat.com> * magnum-auto-healer: Remove use of 'init' methods Instead, register the health checks and cloud provider plugins on controller start up. This avoids side-effects from merely importing the modules - which are polluting the output of '--help' - and is generally "less weird". To do this, we must make the registration methods part of the public API and remove the 'pkg/autohealing/cloudprovider/register' package in favour of a public registration method in the 'pkg/autohealing/cloudprovider/openstack' package. Signed-off-by: Stephen Finucane <stephenfin@redhat.com> --------- Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Seems like the point explaining how to promote images from staging is gone, this commit adds it back, fixes formatting and moves the file into the `docs` directory.
It's a common issue that clusters are deployed with the default `--cluster-name=kubernetes` and later on it's discovered that next deployments on the same cloud will have conflicts when trying to manage LBs of the same namespace and name. This commit aims at allowing to change the cluster-name on a running environment and handling all the renames of the LB resources and their tags.
…ernetes#2569) * define availability zone for snapshot backup * fix to volume backup & restore creation * add doc
The above option seems to be causing CCM to create clients using ServiceAccount from the `kube-system` namespace, so requires users to either run in `kube-system` namespace, or manage 2 ServiceAccounts, one in `kube-system` and other in regular CCM namespace. See [1]. This commit changes this setting. [1] https://github.com/kubernetes/cloud-provider/blob/c3862938334ba18226098015193374fda40ab7a9/options/options.go#L230-L237
The GitHub account brtknr does not exist anymore and our chart linter complains about this. This commit adds Matt and Michał as the maintainers. Co-authored-by: Michał Dulko <mdulko@redhat.com>
I also needed to flip order of mocks in Cinder CSI nodeserver tests and honestly I'm not exactly sure why.
* KEP-1860: Add support for LoadBalancer ipMode * cleaner: use assertEqual for test
* Bump versions for 1.30 * use rc2 for k3s --------- Co-authored-by: Michał Dulko <mdulko@redhat.com>
…rvices (kubernetes#2603) * POC of TargetNodeLabels selector on OpenStack LB * Fix type errors * Update implementation of getKeyValuePropertiesFromServiceAnnotation * gofmt -w -s ./pkg * Polish the code and add documentation --------- Co-authored-by: Ririko Nakamura <ririko.nakamura@outlook.com> Co-authored-by: kayrus <kay.diam@gmail.com>
openshift-ci-robot
added
jira/valid-reference
|
@EmilienM: This pull request references Jira Issue OCPBUGS-34137, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. The bug has been updated to refer to the pull request using the external bug tracker. This pull request references Jira Issue OCPBUGS-34460, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. The bug has been updated to refer to the pull request using the external bug tracker. This pull request references Jira Issue OCPBUGS-34113, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. This pull request references Jira Issue OCPBUGS-35462, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@EmilienM: This pull request references Jira Issue OCPBUGS-34137, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. This pull request references Jira Issue OCPBUGS-34460, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. This pull request references Jira Issue OCPBUGS-34113, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. This pull request references Jira Issue OCPBUGS-35462, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-openstack-csi-cinder e2e-openstack-csi-manila |
|
/override ci/prow/e2e-openstack |
|
@EmilienM: Overrode contexts on behalf of EmilienM: ci/prow/e2e-openstack In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/test e2e-openstack-csi-manila |
|
/test e2e-openstack-csi-manila |
|
/override ci/prow/e2e-openstack-csi-cinder |
|
@EmilienM: Overrode contexts on behalf of EmilienM: ci/prow/e2e-openstack-csi-cinder In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/override ci/prow/e2e-openstack-csi-manila |
|
@EmilienM: Overrode contexts on behalf of EmilienM: ci/prow/e2e-openstack-csi-manila In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
There was a problem hiding this comment.
The failure in the CSI jobs is a known issue (OCPBUGS-31738) and is unrelated to this change.
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EmilienM, mandre The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@EmilienM: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@EmilienM: Jira Issue OCPBUGS-34137: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-34137 has not been moved to the MODIFIED state. Jira Issue OCPBUGS-34460: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-34460 has not been moved to the MODIFIED state. Jira Issue OCPBUGS-34113: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-34113 has not been moved to the MODIFIED state. Jira Issue OCPBUGS-35462: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-35462 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build csi-driver-manila-container-v4.17.0-202406182241.p0.g92021a2.assembly.stream.el9 for distgit csi-driver-manila. |
Commands used:
Then apply patches from:
--use-service-account-credentials=false([occm] Set--use-service-account-credentials=falsekubernetes/cloud-provider-openstack#2572)