Skip to content
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

Release Content for v2.4.1 #296

Merged
merged 35 commits into from
Jul 31, 2024
Merged

Release Content for v2.4.1 #296

merged 35 commits into from
Jul 31, 2024

Conversation

sergeyberezansky
Copy link
Collaborator

No description provided.

sergeyberezansky and others added 30 commits July 3, 2024 18:23
### TL;DR

Updated the Slack notification message in the GitHub workflow to format the `helm upgrade` command as a code block and to include the package path in the footer.

### What changed?

- Changed `SLACK_MESSAGE` to format the `helm upgrade` command as a code block.
- Updated `SLACK_FOOTER` to include the package path.

### How to test?

Trigger a workflow run and verify the Slack notification format and content.

### Why make this change?

Improving readability and context of Slack notifications.

---
fix(CSI-234): leak of wekafs mounts due to bad IsMounted() check
fix(CSI-224,WEKAPP-417375): race condition on multiple volume deletion in parallel
fix(CSI-236): for OCP installations, only 1 machineConfigPolicy was created
Allowed by better multithreaded offline deletion process
fix(CSI-237): increase parralelism of PV deletions
### TL;DR
This change introduces an additional scope 'WEKAPP-\d+' to the PR title linting configuration in our GitHub workflow. This ensures that PR titles can include the WEKAPP identifier.

### What changed?
- Updated the lint_pr.yaml file to recognize and accept 'WEKAPP-\d+' as a valid scope in PR titles.

### How to test?
- Create a PR with 'WEKAPP-xxx' in the title and verify that the linting workflow does not flag it as invalid.

### Why make this change?
This update is necessary to allow PRs that include WEKAPP identifiers in their title, facilitating better tracking and categorization of tasks related to the WEKAPP project.

---
### TL;DR
This PR adds validation functions to check for valid IPv4, IPv6 addresses, and hostnames in the `resetDefaultEndpoints` method and skips endpoints that do not pass validation.

### What changed?
- Introduced `isValidIPv4Address`, `isValidIPv6Address`, and `isValidHostname` functions.
- Updated the `resetDefaultEndpoints` method to utilize these validation functions and skip invalid endpoints.

### How to test?
- Add unit tests to check validation functions with various inputs.
- Test CSI plugin basic sanity in IPv6-enabled Kubernetes cluster against IPv6-only Weka cluster (install, create PVC, create pod)

### Why make this change?
- This change ensures that IPv6 addresses can be specified in configuration
---
wekabot and others added 5 commits July 31, 2024 10:58
### TL;DR

This pull request introduces a conditional configuration to enable `hostNetwork` support for the `csi-wekafsplugin` Helm chart. The changes involve adding conditional checks in the templates to apply the `hostNetwork` settings based on the values provided.

### What changed?

- Added conditional statements to `controllerserver-statefulset.yaml` and `nodeserver-daemonset.yaml` to apply `hostNetwork` settings.
- Updated security context constraints templates to allow host networking when the `hostNetwork` value is true.
- Modified port numbers in the `nodeserver-daemonset.yaml` to accommodate the `hostNetwork` setup.

### How to test?

1. Set `hostNetwork: true` in the `values.yaml` file.
2. Deploy the Helm chart.
3. Verify that the necessary resources are deployed with the `hostNetwork` configuration.

### Why make this change?

This change is motivated by the need to support host networking for specific environments where pod networking might be insufficient or problematic, such as Weka clusters running on top of Kubernetes. Allowing conditional `hostNetwork` configuration provides greater flexibility and control over the networking setup of the CSI driver components.
@graphite-app graphite-app bot requested a review from tigrawap July 31, 2024 11:24
Copy link

graphite-app bot commented Jul 31, 2024

Graphite Automations

"Request reviewers once CI passes" took an action on this PR • (07/31/24)

1 reviewer was added to this PR based on Sergey Berezansky's automation.

@sergeyberezansky sergeyberezansky merged commit 45e7e02 into main Jul 31, 2024
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants