Skip to content

Commit

Permalink
Merge pull request #157 from e0ne/prepare-v.0.4.0
Browse files Browse the repository at this point in the history
Release v0.4.0
  • Loading branch information
moshe010 authored Mar 31, 2021
2 parents eb50b92 + f58386b commit 9fa6531
Show file tree
Hide file tree
Showing 4 changed files with 7 additions and 13 deletions.
4 changes: 2 additions & 2 deletions deployment/network-operator/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
apiVersion: v2
name: network-operator
version: 0.3.0
version: 0.4.0
kubeVersion: '>= 1.17.0'
appVersion: v0.3.0
appVersion: v0.4.0
description: Nvidia Mellanox network operator
type: application
keywords:
Expand Down
6 changes: 3 additions & 3 deletions deployment/network-operator/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ optionally deploy Node Feature Discovery in the cluster. This is enabled via `nf
### SR-IOV Network Operator
Nvidia Network Operator can operate in unison with SR-IOV Network Operator
to enable SR-IOV workloads in a Kubernetes cluster. We provide a helm chart to be used to optionally
deploy [SR-IOV Network Operator](https://github.com/openshift/sriov-network-operator) in the cluster.
deploy [SR-IOV Network Operator](https://github.com/k8snetworkplumbingwg/sriov-network-operator) in the cluster.
This is enabled via `sriovNetworkOperator.enabled` chart parameter.

For more information on how to configure SR-IOV in your Kubernetes cluster using SR-IOV Network Operator
Expand Down Expand Up @@ -222,9 +222,9 @@ the file: `values.yaml`
| `secondaryNetwork.deploy` | bool | `true` | Deploy Secondary Network |

Specifies components to deploy in order to facilitate a secondary network in Kubernetes. It consists of the following optionally deployed components:
- [Multus-CNI](https://github.com/intel/multus-cni): Delegate CNI plugin to support secondary networks in Kubernetes
- [Multus-CNI](https://github.com/k8snetworkplumbingwg/multus-cni): Delegate CNI plugin to support secondary networks in Kubernetes
- CNI plugins: Currently only [containernetworking-plugins](https://github.com/containernetworking/plugins) is supported
- IPAM CNI: Currently only [Whereabout IPAM CNI](https://github.com/dougbtv/whereabouts) is supported
- IPAM CNI: Currently only [Whereabout IPAM CNI](https://github.com/k8snetworkplumbingwg/whereabouts) is supported

##### CNI Plugin Secondary Network

Expand Down
9 changes: 2 additions & 7 deletions scripts/releases/prepare-release.sh
100644 → 100755
Original file line number Diff line number Diff line change
Expand Up @@ -96,10 +96,6 @@ else
exit 1
fi

## Patch deployment files
sed -e s"/image:.*/image: mellanox\/network-operator:$release/" \
-i deploy/operator.yaml

# Patch Helm chart
chart=`echo $release | cut -c 2-`
sed -e s"/appVersion:.*/appVersion: $release/" \
Expand All @@ -113,9 +109,8 @@ git add .
git commit -S -m "Release $release"

if [ -n "$push_remote" ]; then
echo "Pushing gh-pages to $push_remote"
git push "$push_remote" gh-pages

echo "Pushing to $push_remote"
git push "$push_remote"
fi

#
Expand Down
1 change: 0 additions & 1 deletion scripts/releases/update-gh-pages.sh
100644 → 100755
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,6 @@ if [ $# -ne 1 ]; then
exit 1
fi

exit 2
chart="$1"
release=${chart::-4}

Expand Down

0 comments on commit 9fa6531

Please sign in to comment.