WilliamLam.com

VMware Event Broker Appliance (VEBA) v0.6.1

by // Leave a Comment

It has only been about two months since our jammed packed v0.6 release of the VMware Event Broker Appliance (VEBA) solution but the adoption and feedback has been extremely well received by our community. Within the first week or so, we already had a number of folks who had successfully deployed the new version and we started to see new feature enhancements as well as a couple of defects which were quickly resolved. In addition to working through the Github Issues, the team also spent quite a bit of time on creating  more example functions demonstrating how easy it is to author new Knative functions for VEBA across a number of different scripting and programming languages.

Today, we are excited to share a quick update with the release of VEBA v0.6.1 which is a dot release, but it certainly contains several new features that we believe the community can benefit from. For full change log, please refer to v0.6.1 release notes

Here are a few of the new highlighted features:

[Read more...]

USB Network Native Driver for ESXi Fling supports ESXi 7.0 Update 2

by // 5 Comments

Happy to share that our popular USB Network Native Driver for ESXi Fling has now been updated to v1.8 which primarily adds support for ESXi 7.0 Update 2!

This release also resolves a recent PSOD issue that a few folks in the community were hitting when using multiple USB NICs. For more details, please see the change log for more information.

Can I deploy both Tanzu Kubernetes Grid (TKG) and vSphere with Tanzu on same vSphere Cluster?

by // Leave a Comment

A simple question with a simple answer, yes! I have seen this question get asked in various internal Slack channels on whether you can deploy both Tanzu Kubernetes Grid (TKG) and vSphere with Tanzu (formally Project Pacific) on the same vSphere Cluster? If you were an early user of TKG, you may recall that if you attempted to deploy TKG to a vSphere Cluster which already had vSphere with Tanzu enabled, it would prevent you from proceeding. Instead of having to deploy another Kubernetes management control plane, you could simply leverage and connect to the Supervisor Cluster control plane using the TKG CLI and start deploying TKG Workload Clusters.

From a technical standpoint, there is no reason that TKG and vSphere with Tanzu could not co-exist on the same vSphere Cluster. In fact, this request has come up a number of times that the original TKG behavior has been recently updated to now allow for this co-existence. From an exploratory and learning point of view, this is quite useful to be able to try out both solution and not have to dedicate a specific vSphere Cluster for each of the Tanzu Kubernetes (K8s) offerings. A more practical use case that came up recently from a customer was being able to use both solution as a way to consolidate their workloads using a specific Tanzu K8s solution, which makes total sense. Today, there are still some differences in terms of the features and capabilities between TKG and vSphere with Tanzu and depending on your needs, you may have a use case for both in your environment.

[Read more...]