1603598460
Back in the State of the Union, we mentioned an upcoming live meeting open to all. We have scheduled the first of these for Tuesday, October 13th, at 11:30-12:30 Eastern Daylight Time. For this first meeting, the format will be a panel discussion with the Board of Directors, Committee Chairs, and the Executive Director. The event will feature live Q&A from questions submitted from the public. We’ll also take questions in advance.
We recognize that the audience for .NET is global and as we continue to hold these quarterly, we will vary the time to accommodate different time zones. The full recording will always be available afterwards.
#.net
1603598460
Back in the State of the Union, we mentioned an upcoming live meeting open to all. We have scheduled the first of these for Tuesday, October 13th, at 11:30-12:30 Eastern Daylight Time. For this first meeting, the format will be a panel discussion with the Board of Directors, Committee Chairs, and the Executive Director. The event will feature live Q&A from questions submitted from the public. We’ll also take questions in advance.
We recognize that the audience for .NET is global and as we continue to hold these quarterly, we will vary the time to accommodate different time zones. The full recording will always be available afterwards.
#.net
1603594800
I messaged a developer friend to see if he liked my puns, and he said “false.” I told him I didn’t appreciate the cyber boolean.
On tap this week:
On Tuesday, Microsoft announced the release of .NET 5.0 RC 2. With the general release of .NET 5 on November 10, it’s the last release candidate (“near-final,” as Richard Lander puts it). You can download it here (and will also need the latest Visual Studio preview on Windows or Mac).
The biggest news out of the general announcement post? MSI installers are now available for ARM64 (yes!)—however, note the .NET 5 SDK does not contain the Windows Desktop components on ARM64. As a bonus, I learned that ClickOnce is still a thing and available for .NET Core 3.1 and .NET 5 Windows apps.
For being so late in the release cycle, ASP.NET Core was able to ship quite a few Blazor updates for RC 2.
As I’ve written about extensively, Blazor now ships with CSS isolation—the ability to scope styles to only a single component. Previously, when the feature was released in .NET 5 Preview 8, all scoped files were bundled into a big scoped.styles.css
file. If you were styling a lot of components, the bundle could get quite heavy. Now, Blazor produces one bundle for each referenced project or package with the format MyProject.styles.css
. (The official Microsoft doc on CSS isolation, which I’m writing, should be live in the next week or two.)
In addition, RC 2 comes with a bunch of Blazor tooling updates. The pesky static port issue was resolved, you can step out and over async methods, and can debug lazy loaded assemblies. Also, your tools can now throw warnings when using unsupported Blazor Web Assembly APIs from a browser. (This is part of a larger .NET 5 effort that annotates which APIs are supported with a platform compatability analyzer.)
#.net
1616136378
Learn from Docker experts to simplify and advance your app development and management with Docker. Stay up to date on Docker events and new version announcements!
We are sharing a recap of last week’s second quarterly Community All-Hands and the feedback we got from the community.
The Community All-Hands deepen our engagement with the Docker community and bring users, contributors and staff together on a quarterly basis. It is an opportunity for the community to get updates on what we’re working on and align on priorities for the year. It also provides a live forum for the community to engage and ask questions directly to Docker’s executive and community leadership.
In December, we wrote that we wanted to build on the feedback we got after our first Community All-Hands and that we are committed to providing more content, a longer format and make it more interactive for attendees. To this end, we chose to extend the event by 2 hours and include parallel tracks with more speakers and a mix of live keynotes, workshops, lightning talks and regional content. We also picked the Tulu.la video platform to host the event, leveraging their awesome innovative features (eg. integrated chat, multi-casting, WebRTC).
These improvements paid off in an impressive way: we had close to 3,000 unique attendees (including Youtube-live stream viewers), almost tripling the number of attendees who tuned in last time. The turnout was exceptional and the engagement from the community throughout the event was phenomenal.
#docker #devops
1598314680
In the first part of this series, we looked at a few common reasons why organizations deploy Kubernetes on-premises, along with some popular platforms that facilitate such deployments. In this post, we’re going to look at a few best practices involved with deploying Kubernetes on-premises, as well as the arrival of public cloud offerings like the Google Kubernetes Engine on-prem (GKE On-Prem).
In addition to the previously mentioned major factors that drive organizations to consider deploying K8s on-prem — i.e compliance, cloud abilities, and future compatibility — there are probably a couple more we should mention. These include organizations that want to use Kubernetes but don’t want to spend a large amount of money required to host it on a public cloud, and organizations deploying hybrid solutions.
Regardless of your reasons, make no mistake, deploying K8s on-prem is “all hands on deck,” in terms of management, and the first step to getting there is selecting the right “deck” for your deployment. The ability to deploy across multiple environments with a single control plane is a key capability to look for in a Kubernetes platform. This is because while it might seem easy at first, to manage a few clusters in a few different control planes, this becomes quite unsustainable when you start scaling up.
Number two on your checklist needs to be the ability to not only manage and provision infrastructure, but also the ability to integrate well with other on-premises components like networking, storage, monitoring, load balancers, and the like. Remember there’s no public cloud here, so your apps are completely dependent on your infrastructure and how well you manage it. Automating this layer is highly recommended as it makes for quicker, better deployments, as well as self-services. The good news is that most on-prem infrastructure solutions provide the same level of automation as their public cloud counterparts.
Other important factors to consider include operational simplicity and quality of vendor support, involvement and support for Open Source, degree of support for stateful applications, scalability, stability, and licensing costs if any.
Now as opposed to going through with setting up storage, networking, and monitoring and then coming back to security, best practice dictates building it in right from the get-go. This is why as soon as you’ve picked your platform of choice, step two is to start thinking about security and governance. Integrating an image scanning process that scans applications, especially open-source components, libraries, and frameworks, during both the build and run phase is highly recommended.
Using older, more vulnerable versions of software is one of the leading causes of concerns with regards to container security. Implementing version control is a great way around this obstacle and though a lot of the solutions out there are cloud native, there are a few on-premises solutions as well, including a couple that are open source. Using the Center for Internet Security (CIS) benchmarks for Kubernetes runtimes is another best practice that helps establish secure configuration baselines. Additionally, SSL keys or database credentials need to be encrypted and stored centrally with Kubernetes secrets or a third-party Secrets Management service like Vault.
#kublr in the news #kubernetes
1618660800
We’re excited to announce that our next Community All Hands will be on March 11th, 2021 @ 8am PST/5pm CET. This quarterly event is a unique opportunity for Docker staff and the broader Docker community to come together for live company updates, product updates, demos, community shout-outs and Q&A. We had more than 1,500 attendees for our last all-hands and we hope to double that this time.
This all-hands will be particularly special because it will coincide with none other than….you guessed it…Docker’s 8th birthday! For this “birthday edition,” we’re going to make the event extra special.
We’ll start by extending the format from 1 hour to 2 hours to pack in more Docker goodness. The main piece of feedback we got from our last all hands was that it was way too short. We had too much content that we tried to squeeze into 60 minutes. This longer format will give us plenty of time to cover everything we need to cover and let presenters catch their breath
#docker