‘Bridge to Kubernetes’ Leads Container News at Ignite 2020

 In

News

‘Bridge to Kubernetes’ Leads Container News at Ignite 2020

As befits one of the most pop­u­lar open source projects of all time, Kubernetes received its fair share of atten­tion during this week’s Microsoft Ignite 2020 event, led by Bridge to Kubernetes reach­ing gen­er­al avail­abil­i­ty.

Bridge to Kubernetes, which was pre­vi­ous­ly called “Local Process with Kubernetes,” is described as an iter­a­tive devel­op­ment tool that now works with Microsoft’s open source, cross-plat­form Visual Studio Code editor (Visual Studio IDE sup­port is coming), help­ing devel­op­ers write, test and debug microser­vice code on their devel­op­ment work­sta­tions while also being able to con­sume depen­den­cies and inher­it exist­ing con­fig­u­ra­tions from a Kubernetes envi­ron­ment.


Bridge to Kubernetes
[Click on image for larger, animated GIF view.] Bridge to Kubernetes in Animated Action (source: Microsoft).

Or, as its GitHub project page says:

Bridge to Kubernetes extends the Kubernetes perime­ter to your devel­op­ment com­put­er allow­ing you to write, test, and debug microser­vice code while con­nect­ed to your Kubernetes clus­ter with the rest of your appli­ca­tion or ser­vices. With this work­flow, there is no need for extra assets, such as a Dockerfile or Kubernetes man­i­fests. You can simply run your code native­ly on your devel­op­ment work­sta­tion while con­nect­ed to the Kubernetes clus­ter, allow­ing you to test your code changes in the con­text of the larger appli­ca­tion.

The page lists key fea­tures as:

  • Simplifying microser­vice devel­op­ment by elim­i­nat­ing the need to man­u­al­ly source, con­fig­ure and com­pile exter­nal depen­den­cies on a devel­op­ment com­put­er.
  • Easy debug­ging as devel­op­ers can run their usual debug pro­files with the added clus­ter con­fig­u­ra­tion, debug­ging as usual while taking advan­tage of the speed and flex­i­bil­i­ty of local debug­ging.
  • Developing and test­ing end-to-end during devel­op­ment time. Developers can select an exist­ing ser­vice in the clus­ter to route to a devel­op­ment machine where an instance of that ser­vice is run­ning local­ly. A request gen­er­at­ed by the front end of an appli­ca­tion run­ning in Kubernetes will route between ser­vices run­ning in the clus­ter until the spec­i­fied ser­vice to redi­rect is called.

“Microservice appli­ca­tions are com­prised of many ser­vices, often call­ing each other,” Microsoft fur­ther explained in a Sept. 21 blog post announc­ing the prod­uct moving to GA. “Each ser­vice has its own con­fig­u­ra­tion and depen­den­cies, making set­ting up and run­ning the appli­ca­tion local­ly time-con­sum­ing and com­plex.  

“By using Bridge to Kubernetes to con­nect your devel­op­ment work­sta­tion to your Kubernetes clus­ter, you elim­i­nate the need to man­u­al­ly source, con­fig­ure and com­pile exter­nal depen­den­cies on your devel­op­ment work­sta­tion. Environment vari­ables, con­nec­tion strings and vol­umes from the clus­ter are inher­it­ed and avail­able to your microser­vice code run­ning local­ly.”

The com­pa­ny said sup­port for Bridge to Kubernetes on any Kubernetes clus­ter is ini­tial­ly avail­able in VS Code, soon to be fol­lowed by the Visual Studio IDE.

More infor­ma­tion can be found in:

Another GA announce­ment con­cerned the new Azure Policy add on for Azure Kubernetes Service (AKS.)

“Azure Policy for Kubernetes can con­trol the details of the resources that a user cre­ates within a clus­ter, so that, for exam­ple, no one can acci­den­tal­ly expose a ser­vice on the public inter­net that allows mali­cious attack­ers to bit­coin mine on your clus­ter,” Microsoft said in a anoth­er blog post this week titled “Enterprise grade Kubernetes on Azure.”

“Azure is an indus­try leader in cloud policy and donat­ed the ini­tial imple­men­ta­tion of GateKeeper, the Kubernetes Policy con­troller to the Open Policy Agent and CNCF. It makes sense then that we are also the first cloud to make Kubernetes Policy gen­er­al­ly avail­able in our Azure Kubernetes Service. Policy is an inte­gral part of secur­ing Kubernetes, and now our enter­prise cus­tomers can rely on the ser­vice guar­an­tees that come with a gen­er­al­ly avail­able ser­vice.”

Yet more Kubernetes announce­ments addressed enhanced pro­tec­tion for con­tain­ers. “As con­tain­ers and specif­i­cal­ly Kubernetes are becom­ing more widely used, the Azure Defender for Kubernetes offer­ing has been extend­ed to include Kubernetes-level policy man­age­ment, hard­en­ing and enforce­ment with admis­sion con­trol to make sure that Kubernetes work­loads are secured by default,” Microsoft said in its Book of News. “In addi­tion, con­tain­er image scan­ning by Azure Defender for Container Registries will now sup­port con­tin­u­ous scan­ning of con­tain­er images to min­i­mize the exploitabil­i­ty of run­ning con­tain­ers.”

Another update to AKS was detailed thusly: “The AKS Stop/Start clus­ter fea­ture now in public pre­view allows AKS cus­tomers to com­plete­ly pause an AKS clus­ter and pick up where they left off later with a switch of a button, saving time and cost. Previously, a cus­tomer had to take mul­ti­ple steps to stop or start a clus­ter, adding to oper­a­tions time and wast­ing com­pute resources. The stop/start fea­ture keeps clus­ter con­fig­u­ra­tions in place and cus­tomers can pick up where they left off with­out recon­fig­ur­ing the clus­ters.”

Other pre­views were announced for Azure Arc-enabled Kubernetes and AKS on Azure Stack HCI.

Azure Arc helps users extend Azure man­age­ment to any infra­struc­ture while enabling deploy­ment of Azure data ser­vices any­where.


Azure Arc enabled Kubernetes clusters alongside AKS clusters
[Click on image for larger view.] Azure Arc enabled Kubernetes clusters alongside AKS clusters (source: Microsoft).

“Azure Arc extends Azure man­age­ment to infra­struc­ture resources such as Windows and Linux Servers, SQL Servers and Kubernetes clus­ters run­ning across on-premis­es dat­a­cen­ters, mul­ti­cloud and edge,” Microsoft said. “Azure Arc also enables deploy­ment of Azure data ser­vices, such as Azure SQL Managed Instance and Azure PostgreSQL Hyperscale, on any infra­struc­ture of choice.”

More infor­ma­tion can be found in a post pub­lished this week titled “Azure Arc enabled Kubernetes with GitOps.”

Concerning AKS on Azure Stack HCI, Microsoft said the ser­vice avail­able in pre­view “enables devel­op­ers and admins to deploy and manage con­tainer­ized apps on Azure Stack HCI. Customers can take advan­tage of its con­sis­tent expe­ri­ence with AKS on Azure, extend to Azure with hybrid capa­bil­i­ties, run apps with con­fi­dence with built-in secu­ri­ty, and use famil­iar tools to mod­ern­ize Windows apps.”

Azure Stack HCI is a ser­vice for for hybrid, famil­iar hyper­con­verged infra­struc­ture.

Microsoft documentation states: “Azure Kubernetes Service on Azure Stack HCI is an on-premis­es imple­men­ta­tion of the pop­u­lar Azure Kubernetes Service (AKS) orches­tra­tor, which auto­mates run­ning con­tainer­ized appli­ca­tions at scale. Azure Kubernetes Service is now in pre­view on Azure Stack HCI, making it quick­er to get start­ed host­ing Linux and Windows con­tain­ers in your dat­a­cen­ter.”

Microsoft Ignite 2020 start­ed Tuesday and con­cludes today Sept 24. For more cov­er­age from Virtualization & Cloud Review and sister sites, see:

About the Author

David Ramel is an editor and writer for Converge360.

Virtualization & Cloud Review source|articles

Recommended Posts
0

Start typing and press Enter to search