Dear LINBIT SDS on Kubernetes users,
We've recently released updates for our Kubernetes Operator.
In version v2.3.0 of our next-generation Operator we've added a lot of
usability improvements. There are now shortcuts for editing most
operator-controlled containers. So instead of having to write a patch,
you can provide a "podTemplate" for the container.
There are also now toggles for specific components, such as the High
Availability Controller, so you can disable the deployment if you
really need to.
There is also now the option to use TLS with DRBD: if LINSTOR is
configured to user internal TLS, you can in addition set
.spec.internalTLS.tlsHandshakeDaemon=true in the Satellite
Configuration, which automatically deploys the needed user space
component. If you then set "DrbdOptions/Net/tls: yes" in LINSTOR, you
automatically get encrypted DRBD replication.
In order to ease deployment, we have removed the default NetworkPolicy
as it proved to be troublesome with some CNI plugins. We have also
made sure that all resources work on older Kubernetes versions, so
LINBIT SDS works out of the box with Kubernetes 1.20 and newer.
There is also now a new helm chart to deploy the LINSTOR Operator,
along with the workloads. They are packaged as two separate charts to
work around some Helm limitations regarding CRDs. To install LINSTOR
Operator v2 with helm, run:
helm repo add linstor https://charts.linstor.io
helm install linstor-operator linstor/linstor-operator \
--set imageCredentials.username=$MY_LINBIT_USER \
--set imageCredentials.password=$MY_LINBIT_PASSWORD \
--wait
helm install linbit-sds linstor/linbit-sds
Most configuration is handled by the linbit-sds chart, so check out
"helm show values linstor/linbit-sds" to see the available options.
For Operator v1, there are only the updated component images, which
are shared with Operator v2.
Also, watch out for the Upgrade Guide for Operator v1 deployment,
which will be announced separately soon.
To get specific instructions to apply the update, check our users guide: [1]
Source code is, as always, available upstream. [2]
Best regards,
Moritz
[1]: https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade
[2]: https://github.com/piraeusdatastore/piraeus-operator
Operator v2.3.0 Changelog
-------------------------
### Added
- Add a new option `.spec.internalTLS.tlsHandshakeDaemon` to enable
deployment of `tlshd` alongside the LINSTOR Satellite.
- Shortcuts to configure specific components. Components can be
disabled by setting `enabled: false`, and the deployed workload can be
influenced using the `podTemplate` value. Available components:
- `LinstorCluster.spec.controller`
- `LinstorCluster.spec.csiController`
- `LinstorCluster.spec.csiNode`
- `LinstorCluster.spec.highAvailabilityController`
- Shortcut to modify the pod of a satellite by adding a
`LinstorSatelliteConfiguration.spec.podTemplate`, which is a shortcut
for creating a `.spec.patches` patch.
### Changed
- Fixed service resources relying on the default protocol version.
- Moved NetworkPolicy for DRBD out of default deployed resources.
- Updated images:
* LINSTOR 1.25.1
* LINSTOR CSI 1.3.0
* DRBD Reactor 1.4.0
* Latest CSI sidecars
- Add a default toleration for the HA Controller taints to the operator.
Operator v1.10.8 Changelog
--------------------------
### Changed
- Default images:
* LINSTOR 1.25.1
* LINSTOR CSI 1.3.0
* DRBD 9.1.17
* DRBD Reactor 1.4.0
* Latest CSI sidecars
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user
We've recently released updates for our Kubernetes Operator.
In version v2.3.0 of our next-generation Operator we've added a lot of
usability improvements. There are now shortcuts for editing most
operator-controlled containers. So instead of having to write a patch,
you can provide a "podTemplate" for the container.
There are also now toggles for specific components, such as the High
Availability Controller, so you can disable the deployment if you
really need to.
There is also now the option to use TLS with DRBD: if LINSTOR is
configured to user internal TLS, you can in addition set
.spec.internalTLS.tlsHandshakeDaemon=true in the Satellite
Configuration, which automatically deploys the needed user space
component. If you then set "DrbdOptions/Net/tls: yes" in LINSTOR, you
automatically get encrypted DRBD replication.
In order to ease deployment, we have removed the default NetworkPolicy
as it proved to be troublesome with some CNI plugins. We have also
made sure that all resources work on older Kubernetes versions, so
LINBIT SDS works out of the box with Kubernetes 1.20 and newer.
There is also now a new helm chart to deploy the LINSTOR Operator,
along with the workloads. They are packaged as two separate charts to
work around some Helm limitations regarding CRDs. To install LINSTOR
Operator v2 with helm, run:
helm repo add linstor https://charts.linstor.io
helm install linstor-operator linstor/linstor-operator \
--set imageCredentials.username=$MY_LINBIT_USER \
--set imageCredentials.password=$MY_LINBIT_PASSWORD \
--wait
helm install linbit-sds linstor/linbit-sds
Most configuration is handled by the linbit-sds chart, so check out
"helm show values linstor/linbit-sds" to see the available options.
For Operator v1, there are only the updated component images, which
are shared with Operator v2.
Also, watch out for the Upgrade Guide for Operator v1 deployment,
which will be announced separately soon.
To get specific instructions to apply the update, check our users guide: [1]
Source code is, as always, available upstream. [2]
Best regards,
Moritz
[1]: https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade
[2]: https://github.com/piraeusdatastore/piraeus-operator
Operator v2.3.0 Changelog
-------------------------
### Added
- Add a new option `.spec.internalTLS.tlsHandshakeDaemon` to enable
deployment of `tlshd` alongside the LINSTOR Satellite.
- Shortcuts to configure specific components. Components can be
disabled by setting `enabled: false`, and the deployed workload can be
influenced using the `podTemplate` value. Available components:
- `LinstorCluster.spec.controller`
- `LinstorCluster.spec.csiController`
- `LinstorCluster.spec.csiNode`
- `LinstorCluster.spec.highAvailabilityController`
- Shortcut to modify the pod of a satellite by adding a
`LinstorSatelliteConfiguration.spec.podTemplate`, which is a shortcut
for creating a `.spec.patches` patch.
### Changed
- Fixed service resources relying on the default protocol version.
- Moved NetworkPolicy for DRBD out of default deployed resources.
- Updated images:
* LINSTOR 1.25.1
* LINSTOR CSI 1.3.0
* DRBD Reactor 1.4.0
* Latest CSI sidecars
- Add a default toleration for the HA Controller taints to the operator.
Operator v1.10.8 Changelog
--------------------------
### Changed
- Default images:
* LINSTOR 1.25.1
* LINSTOR CSI 1.3.0
* DRBD 9.1.17
* DRBD Reactor 1.4.0
* Latest CSI sidecars
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user